Hi,
Tying to get nginx, node and Cloudflare to work together. I think everything is fine except that Im getting redirected and a slash is added to the end of the root URL.
Example:https://repick.co// with an extra slash at the end. It can get appended on the same spot also on longer URLs so its not always on the end.
But if I go directly to my public IP it works perfectly after accepting the cert 188.149.51.207
I wonder is this a problem with node, nginx or Cloudflare.
Since im not allowed to post more than two links, heres an pastebin with result of WGET and my nginx config:
sandro
February 2, 2020, 4:06pm
2
Whats your encryption mode on Cloudflare? Flexible? If so, switch that to “Full strict”.
sandro
February 2, 2020, 4:09pm
4
So you have set it to “Full strict” and your IP address ends in 207? Correct?
Any page rules in place?
Yes, its set to full strict mode. I also enabled:
Always Use HTTPS
That is correct yes!
Where can I find page rules?
sandro
February 2, 2020, 4:12pm
7
sandro
February 2, 2020, 4:17pm
10
Hmm, that all actually looks all right. I assume you wont have any workers in place either.
I am not sure what that rewrite statement in your server configuration does. Can you comment it out and check if that fixes it?
I tried adding that to remove trailing slashes but it didn’t help. I removed it again now but the same result. That is odd. I have no clue if the problem is within Cloudflare or on my server.
Strange that it works perfectly fine if I go directly to my public IP:https://188.149.51.207
I do not have any workers in place either, that’s correct.
sandro
February 2, 2020, 4:22pm
13
Do you have access to the server logs?
Just tried adding logs to the http block in my nginx config like this:
error_log logs/error.log info;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log logs/access.log main;
but the logs folder is empty even if I restart nginx and trying accessing the site.
sandro
February 2, 2020, 4:33pm
15
Even if you access the site directly?
sdayman
February 2, 2020, 4:33pm
16
That’s a mystery. On my first direct try, it complained about the certificate on the server, but after disabling certificate check, there was no redirect. What certificate do you have on the server?
sandro
February 2, 2020, 4:35pm
17
The site works fine when going directly. It shouldnt be page rules nor workers. Nameservers are also correct, so either it is some obscure issue with Cloudflare or the webserver returns different content to Cloudflare.
1 Like
Hum, very strange. This is the cert I use. I made it under the Origin Server tab in cloudflare
-----BEGIN CERTIFICATE-----
Can it be a permissions problem on the file in the server?
sandro
February 2, 2020, 4:37pm
19
@nicklas2 , though I dont think it would solve it, could you try to purge your entire Cloudflare cache?
Also, what about my log question?
Hum, yep the logs folder is empty even though I access the page directly on the IP.
Tried running both:
Its a Mac, therefor its installed via homebrew.
How to I purge Cloudflare cache? That would be interesting to try.
Edit:
Not allowed to post more here since its my first day as member. @sandro @sdayman
Edit2:@sandro
That was me causing the port hangup in the begninning of the logs since I tried just starting nginx again.
Edit3:
Why does it show like:http://repick.co ” “Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/ )” “69.162.124.234”http://repick.co ” “Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/ )” “69.162.124.234”
Looks like it is making a get over http that is shouldent? and what does uptimerobot.com has to do with this?
Edit 4:@sandro I changed the block in the nginx config to:
server {
listen 443 ssl;
server_name localhost;
ssl_certificate /usr/local/etc/nginx/repickssl/cert.pem;
ssl_certificate_key /usr/local/etc/nginx/repickssl/key.pem;
# location / {
# proxy_pass http://localhost:3000;
# proxy_http_version 1.1;
# proxy_set_header Upgrade $http_upgrade;
# proxy_set_header Connection 'upgrade';
# proxy_set_header Host $host;
# proxy_cache_bypass $http_upgrade;
# }
location / {
root /usr/local/var/www;
}
}
Now I see the standard nginx page again and dident get redirect issue. it also shows https://repick.co as secure.
However it still adds the extra slash to the end. That is the root cause since the real website will redirect back to repick.co then Cloudflare (or whatever it is) will redirect to repick.co// and the loop has started.
highly confused…