Desktop client ip not domain

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
1

Dear

A while ago i changed from an nginx server as reverse proxy with letsencrypt that provided an ssl certificate to an iis reverse proxy with certify the web that provides an ssl certificate.

After the change i tried on another pc to connect with my nextcloud server using the desktop client but this doesn’t use the domain name but goes to my ip of my nextcloud internally.
As result i can’t connect with my nextcloud using the desktop client. When i go to my domain name in my webbrowser everything works just fine.

Thanks in advance!

Kind regards

Kevin

1 Like
2

What do you mean by this? You should be using the FQDN to connect, even locally.

3

I know and when I do this it automatically opens the browser en the fqdm is redirected to an internal ip…
So something is going wrong but for now I don’t know what is…

4

So it does or doesn’t work in the browser?

5

In the browser it does work.
When setting up the desktop software you need to authorize. So first you give in the fqdn after that it opens a browser tab. And here it goes wrong when I try to authorize it automatically goes to the internal ip and not the fqdn

6

Maybe check config.php for value of

‘overwrite.cli.url’ => ’ … ’

If it points to your internal IP, edit it to point to your fqdn.

7

This line points to my fqdn…
Only thing in my config that points to my ip is the ip in the array of trusted domains.
When i delete this my nextcloud ain’t working anymore…

8

Anyone that has an idea?..

9

Nextcloud only supports Apache and nginx. Whether it will work behind an IIS reverse proxy, I don’t know. Maybe someone else knows. Just doing a brief search, I’m seeing a lot of odd issues, and not a lot of answers.

You may want to reconsider changing to IIS.

For any further troubleshooting, you’ll need to post your configs and give some details about IIS.

10

I had a similar problem a while ago. My nextcloud is although behind a reverse proxy which does tls offloading. The nextcloud sever behind the proxy is running on a different high port (8090) so I set the following values in the nextcloud config:

'trusted_domains' => 
 array (
    0 => '127.0.0.1:8090',
    1 => '10.10.10.30:8090',
    2 => 'cloud.domain.tld',
 ),
 'trusted_proxies' => 
 array (
     0 => '0.0.0.0/0',
 ),
 'forwarded_for_headers' => 
  array (
     0 => 'HTTP_X_FORWARDED_FOR',
 ),
'overwrite.cli.url' => 'https://cloud.domain.tld',
'overwritehost' => 'cloud.domain.tld',
'overwriteprotocol' => 'https',

On the reverse proxy I have set the following headers to be added to the request:

 X-Forwarded-For [[src-ip]]
 X-Forwarded-Proto https
 X-Real-IP [[src-ip]]

I hope that may help you.