We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstream ws { server 104.16.19.234:443; server 104.16.18.234:443; server 104.16.10.234:443; server 104.16.11.234:443; } server { listen 80; location /{ proxy_pass_header Server; proxy_pass https://ws; proxy_set_header Host "cloudflareapi.com"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; } }
upstream ws { server 104.16.19.234:443; server 104.16.18.234:443; server 104.16.10.234:443; server 104.16.11.234:443;
}
server { listen 80;
location /{ proxy_pass_header Server; proxy_pass https://ws; proxy_set_header Host "cloudflareapi.com"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; } }
403 Forbidden cloudflare-nginx
The text was updated successfully, but these errors were encountered:
hi f4nff,
Could you give more detail of this issue, you can output $upstream_status in access.log to check whether 403 is responsed by backend server.
$upstream_status
Also you can request backend server directly to check.
Sorry, something went wrong.
add
proxy_ssl_server_name on; proxy_ssl_name "www.cloudflare.com";
ok~
add proxy_ssl_server_name on; proxy_ssl_name "www.cloudflare.com";
think it resolved, I am closing this issue. You can reopen this issue if having any problem.
No branches or pull requests
The text was updated successfully, but these errors were encountered: