HTTP Error 403 on New NGINX Server

Discussion in 'ISPConfig 3 Priority Support' started by Gray Consulting, Mar 3, 2024.

  1. Gray Consulting

    Gray Consulting Member HowtoForge Supporter

    Greetings all -

    Longtime, happy ISPConfig user, just built new server with NGINX (I was always an Apache guy; adjusting for my developer)
    New server is on AWS instance, server checks report everything ok. Using Route 53 with standard setup; I can ping via IP and domain name; FTP client connects & works fine; SSH sessions work fine. (All my previous ISPC servers were set up similarly, and work fine.) Setup of new site in ISPConfig went fine, no errors reported, checks report ok.
    Whenever I add a new site, and test the new site, however, I get Error 403, and/or "connection unavailable".
    No errors in /var/log/nginx/error.log or access.log. This is the only (seemingly) relevant error I could find, in /var/log/ispconfig/httpd/(domainname)/error.log

    Code:
     ... access forbidden by rule, client: 116.203.62.36, server: (domainname), request: "GET / HTTP/1.1", host: "(domainname)" 
    I have no firewall setup in ISPConfig or AWS. NS lookups report as expected; resolvers return expected values.
    Not even sure where to go from here. Any help would be greatly appreciated!
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Do you use any custom Nginx directives in that website or have you customized the nginx vhost file template?
     
  3. Gray Consulting

    Gray Consulting Member HowtoForge Supporter

    Hi Till -
    Apologies for the slow response; too many plates spinning.
    The good news is, I found the error - I had not opened inbound ports in AWS. Working well now, just gotta sort out my SSL cert.
    Call this one closed ;)
     
    till likes this.

Share This Page