0

New poster here so unsure if this is the correct stack exchange.

But basically, I use NPM (Nginx Proxy Manager) to direct internet traffic to various VMs running on my hub server running proxmox.

Whenever I try to connect to an internet SSL-based web application such as the web UI for NPM or Nextcloud, my web browser gives me a connection error. However, when I try to connect to the same domain that gave me a connection error through a VPN connection, the connection works just fine.

Why can't I connect to my own domains while being just on my normal connection no VPN?

Just a few things: Everything is hosted on 1 single public IP.

Every web app has its own VM on an unfirewalled proxmox server (Every vm has its own built-in firewall, with relevant ports forwarded)

My domain name is: ambient-sky.co.uk

The VPN I use is just opera GXs proxy server.

Any ideas/tips would be helpful as I've never experienced this before.

If any logs or configurations are needed then I'd be happy to oblige.

No VPN

VPN enabled

7
  • Does this answer your question? Loopback to forwarded Public IP address from local network - Hairpin NAT
    – vidarlo
    May 20, 2023 at 13:49
  • No. Since I'm not using Hairpin NAT. Nor do I even know what that is :) May 20, 2023 at 20:07
  • 1
    Do you use NAT? You include no information on your topology. My suspicion is that your problem is that you don't use hairpin NAT - hence the duplicate. Please read it.
    – vidarlo
    May 20, 2023 at 20:16
  • to solve the problem, we need: /etc/network/interfaces, /etc/nginx/ where we see how you proxy it, the rest we can figure out later but using admin panel will not make it easier
    – djdomi
    May 21, 2023 at 8:59
  • @vidarlo Probably gonna need an explanation on NAT. I also have no idea what topology means. Do you mean my setup? I thought I explained that.. I did read it, and understood none of it. Please reclarify May 21, 2023 at 11:13

1 Answer 1

0

Okay, I'm not 100% sure if it was something I did or if my ISP forked up somewhere along the line. But now its working just fine

I sent an email to them asking if it was something on their end on why I couldn't locally resolve my own public IP. Woke up today, and now I can for some reason and my Domains are working locally again.. I never had a response from them on my email.

Sorry if I wasted anyone's time.

1
  • most dns changes are taken 24 till 96 hours to get through the world
    – djdomi
    May 21, 2023 at 18:18

Not the answer you're looking for? Browse other questions tagged .