DNS Entries Pointing to IP Address on My Machine Getting 404s

Hello! I have a recent issue with my domain name, http://www.rcignoniplex.com, registered at NameCheap, where any DNS entries I add on Cloudflare are getting 404s - http://rcignoniplex.com and http://requests.rcignoniplex.com. They are both pointed at my external IP Address. This seems to have started randomly a day or two ago. I’m trying to reverse proxy into a local website I have on my machine, and this is rendering it inaccessible, to where the Nginx Proxy Manager service I have running cannot issue a certificate for it with LetsEncrypt because it gets a 400-level response.

It is worth mentioning that I use a VPN through Private Internet Access, but this problem persists both when the VPN is on and off. My VPN is set up to use the PIA DNS and I am using a dedicated IP Address - Docker uses my system’s DNS Address, and the IP Address I’m using for my DNS names is what Google reports, which is my actual external IP, not the VPN one - all of my apps bypass my VPN except for my P2P client.

Here is my current DNS Management setup:

I have confirmed that my Cloudflare Nameservers are properly configured.

My ports 80 and 443 are being forwarded by AT&T (BGW210-700).

My Nginx Proxy Manager running out of localhost:81 is pointing to my local IPV4 address port 5055, running Overseerr, for the requests.rcignoniplex.com subdomain.

I’ve also created firewall exceptions for Ports 5055, 81, 80, and 443, where I have these local websites hosted.

Kind of at a loss for what might be going on here, so I’m taking it to the community. Thanks!

A 404 error means that Cloudflare connects to the server but nginx is not finding the location that it should be serving. I would check your nginx config

1 Like

Thanks for the reply!! I have nginx and overseerr both configured via Docker. I point the proxy at my local IPv4 address and have the Cloudflare DNS pointed at my external IPv4 Address. Not sure if running these out of docker is not allowing NPM to communicate with Docker… I can’t even get the generic “congratulations” message to work. If it helps, here’s my docker-compose.yml and my config for the proxy. Not sure where I would find any other configs.

version: '3'

services:
  overseerr:
    image: sctx/overseerr:latest
    container_name: overseerr
    environment:
      - LOG_LEVEL=info
      - TZ=America/Chicago
    ports:
      - 5055:5055
    volumes:
      - /path/to/appdata/config:/app/config
    restart: unless-stopped

  nginxproxymanager:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: nginxproxymanager
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    restart: unless-stopped```

```# ------------------------------------------------------------
# requests.rcignoniplex.com
# ------------------------------------------------------------
server {
  set $forward_scheme http;
  set $server         "192.168.1.83";
  set $port           5055;

  listen 80;
  listen [::]:80;

  server_name requests.rcignoniplex.com;

  # Asset Caching
  include conf.d/include/assets.conf;

  # Block Exploits
  include conf.d/include/block-exploits.conf;

  access_log /data/logs/proxy-host-2_access.log proxy;
  error_log /data/logs/proxy-host-2_error.log warn;

  location / {
    # Proxy!
    include conf.d/include/proxy.conf;
  }
  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Figured this out! World Wide Web Publishing Service was running in services.msc and was listening on Port 80, causing the issue. Stopped that service and voila.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.