Install Nginx as a Reverse Proxy on Fedora 27

brandon220

Another question:
When you access Nextcloud with https and the site check shows that everything passes

But, when you place it behind Nginx, it "breaks"

I am trying to understand what is happening behind the scenes to cause the error. Is anyone else seeing this happen on their instances?

JaredBusch

@brandon220 said in Install Nginx as a Reverse Proxy on Fedora 27:

Another question:
When you access Nextcloud with https and the site check shows that everything passes

But, when you place it behind Nginx, it "breaks"

I am trying to understand what is happening behind the scenes to cause the error. Is anyone else seeing this happen on their instances?

This is not broken. it is simply a warnign about something..

What do you mean broken?

brandon220

@JaredBusch I should not have said "broken". It is not causing any issues that I can see. Just not sure what changes that makes it give the warning. Is this one to ignore?

JaredBusch

@brandon220 said in Install Nginx as a Reverse Proxy on Fedora 27:

@JaredBusch I should not have said "broken". It is not causing any issues that I can see. Just not sure what changes that makes it give the warning. Is this one to ignore?

Read the message.

It says that it does not see a configuration related to LetsEncrypt.

If you are using a proxy, the proxy handles the cert.

scottalanmiller

@brandon220 said in Install Nginx as a Reverse Proxy on Fedora 27:

@JaredBusch I should not have said "broken". It is not causing any issues that I can see. Just not sure what changes that makes it give the warning. Is this one to ignore?

Purely a warning, and not really a good one. It doesn't apply to you, so that makes it a bad warning.

black3dynamite

@brandon220 said in Install Nginx as a Reverse Proxy on Fedora 27:

Another question:
When you access Nextcloud with https and the site check shows that everything passes

But, when you place it behind Nginx, it "breaks"

I am trying to understand what is happening behind the scenes to cause the error. Is anyone else seeing this happen on their instances?

If you want to remove that warning, add the following in the server block

location = /.well-known/carddav {
      return 301 $scheme://$host/remote.php/dav;
    }
    location = /.well-known/caldav {
      return 301 $scheme://$host/remote.php/dav;
    }

travisdh1

It's now 2/15/2024 with Fedora 39, and this is still working.

Just setup a new reverse proxy.