January 28, 20242 yr I have NPM running on a custom docker network and having the proxy service target various docker containers (also on the same custom docker network). I have setup a ubuntu server VM and am attempting to install discourse. I get docker installed on the VM and start to install discourse, at one point during the initial install it asks for the qualified domain name but i get the following error Hostname for your Discourse? [discourse.example.com]: forum.mydomain.net Checking your domain name . . . WARNING: Port 443 of computer does not appear to be accessible using hostname: WARNING: Connection to (port 80) also fails. This suggests that forum.mydomain.net resolves to some IP address that does not reach this machine where you are installing discourse. The first thing to do is confirm that forum.mydomain.net resolves to the IP address of this server. You usually do this at the same place you purchased the domain. If you are sure that the IP address resolves correctly, it could be a firewall issue. A web search for "open ports YOUR CLOUD SERVICE" might help. This tool is designed only for the most standard installations. If you cannot resolve the issue above, you will need to edit containers/app.yml yourself and then type this is what ubuntu says for system info System information as of Sun Jan 28 07:35:54 AM UTC 2024 System load: 0.5126953125 Usage of /: 45.9% of 13.16GB Memory usage: 6% Swap usage: 0% Processes: 125 Users logged in: 0 IPv4 address for docker0: 172.17.0.1 IPv4 address for enp1s0: 10.30.20.150 ive run the following commands from my NPM container to see if i can reach the server # curl -sS https://10.30.20.150:443/ >/dev/null && echo "Container is reachable" curl: (7) Failed to connect to 10.30.20.150 port 443 after 18698 ms: Couldn't connect to server # curl -sS http://10.30.20.150:80/ >/dev/null && echo "Container is reachable" curl: (7) Failed to connect to 10.30.20.150 port 80 after 3048 ms: Couldn't connect to server As a note my router has port 80,81, and 443 forwarded to NPM. When assigning ports to docker containers I always see what ports are not used and assign free ports then target that port when adding a proxy host. Im wondering if this is a conflict with the VM's port of 443 though even though when setting up Ubuntu I have assigned a static IP, (which is different from the IPs currently assigned to docker). My dockers are running on a custom docker network, my VM I assigned to br0 and is running virtio-net. One of the last notes I'd like to add is that when I check my DHCP status within Pfsense I do not see the VM listed, but when I check the arp tables I can see 10.30.20.150 linked to the mac address assigned in the VM settings. Currently at a loss on what do do next to diagnose further. Any recommendations? Edited January 29, 20242 yr by randypfau
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.