Install Nginx as a Reverse Proxy on Fedora 27

JaredBusch

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

Trying to get this to work tonight. The nextcloud.conf is copied on the Nginx server. I changed the server_name and the proxy_pass. Everything else is unchanged. When I run the nginx-t to verify, it returns

nginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/conf.d/nextcloud.conf:4
nginx: configuration file /etc/nginx/nginx.conf test failed

I have researched for a few hours and cannot "see" where the issue is. I am in need of some guidance.

You likely missed a semicolon to close a line.

brandon220

@JaredBusch I looked at the config till my eyes went cross and didn’t notice that. I’ll check again later and see. I looked at the logs and they don’t really give any clues.

JaredBusch

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

@JaredBusch I looked at the config till my eyes went cross and didn’t notice that. I’ll check again later and see. I looked at the logs and they don’t really give any clues.

That error you posted tells you that. On that line you didn’t close it, so it thinks you next line is another parameter of the command.

brandon220

The problem was the items such as $remote_addr did not copy at all. They were missing. The config passed. Did the certbot and all went fine. If I go to https://nc.domain.com the site loads properly. If I go to http://nc.domain.com the site redirects and loads fine. Both work and cert loads in browser. However, if I go to nc.domain.com, it returns a blank page and shows https://localhost in the browser. I have the fqdn set up on the NC server and the Nginx. Not sure where this is coming from.

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.