Issue configuring AMP with dedicated Nginx Proxy Manager

OS Name/Version: Ubuntu 24.04.3 - via VM on TrueNas Scale ElectricEel-24.10.2.3

Product Name/Version: AMP Release “Phobos” v2.6.3

Problem Description: After being away from AMP (and gaming in general) for a bit some friends and I decided to start up a “forever world” of Valheim. So I refreshed my knowledge of AMP and got to work. I recently built/rebuilt my home NAS server after the old power supply failed. In doing so the Server was much more powerful and can handle hosting more applications and not just act as a personal cloud, with that in mind I decided I would start by running a dedicated Nginx Proxy Manager instance. I followed a few different procedures for setting up NPM, which where all basically the same, but here is my process.

  1. The Dockge app was installed via the applications section of TrueNAs
  2. Via the Nginx Proxy Manager website I created a Docker via Dockge on my TrueNAS Machine
    1. I did update the ports so that they are directed to not the standard ‘shared’ ports. ie 85:80, 8443:443, and 8181:81
    2. The ports of my TrueNAS machine are also updated so that they are not directed to ‘shared’ ports.
  3. I have a personal domain via squarespace
    1. blazewyo.me
    2. Custom DNS record for ‘nas’ pointed to IP of the NPM server
  4. I created a Cloudflare account to host the DNS of that Domain
    1. In doing so I updated the Nameservers on Squarespace to the generated Cloudflare Nameservers.
  5. For the NPM setup I followed the Configuration Guide via Dan - Nginx Proxy Manager | Dan's Wiki
    1. On my local network, Ubiquiti Unifi (Unifi OS 4.3.6) I created a DNS record for npm.nas.blazewyo.me and pointed it at the IP address of my TrueNAS Machine. I also added a DNS record for valheim1.nas.blazewyo.me.
    2. Within NPM I created a SSL Certificate and Proxy Host, again following the guide by Dan - both of which are listed as Active and Online in Nginx Proxy Manager.
      1. SSL Certificate = *.nas.blazewyo.me and nas.blazewyo.me
      2. Proxy Host = valheim1.nas.blazewyo.me = TrueNAS IP:AMP Valheim Instance Port
      3. Upon testing this again later I found that when adding a SSL Certificate for *.nas.blazewyo.me and selecting “test server reachability” I gave an error: “There is a server found at this domain but it returned an unexpected status code Connection timed out.. Is it the NPM server? Please make sure your domain points to the IP where your NPM instance is running.” I did not conduct the “test” the first time I added the SSL Cert.
  6. AMP Installation - TrueNAS VM - Ubuntu 24.04.3
    1. Standard install - selected no on HTTPS since I was setting up a dedicated nginx
    2. Once Running → Configuration → System Settings
      1. Checked Using Reverse Proxy to ON
    3. Created a Valheim Instance - used Game Port for Proxy Host above
      1. Valheim Configuration
        1. Checked “Server is Public” to on and updated Server Password
      2. Started Instance and it is Running

And that is where I am at, I cannot access the game. I have attempted via both the Instance Connection Link and also adding the server in Valheim. In Valheim I tried adding the Server as the IP address to the TrueNAS machine and the VM Instance of AMP, plus adding the server via the URL of the NPM Proxy Host. When adding the server via the URL I was given an error of “DNS Lookup failed!” I am stuck at if this is an AMP issue, Nginx Proxy Manager Issue, Cloudflare issue, SquareSpace issue, or Unifi issue. Thoughts?

Additional Information

  1. I have ran an AMP game server in the past; for Minecraft, Valheim, Icarus, and a few others. But previously I was running AMP on a dedicated machine, also running Ubuntu. That was the only thing that computer did, was run AMP. And at that time I would just open specific ports in Unifi for the Instance ports, it worked, but was not very secure. I do not believe I was running nginx or anything at the time.
  2. I want to run a hosted version of NPM as I eventually want to migrate other apps to be hosted via NPM; HomeAssistant, Plex, etc.
1 Like

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