NGINX Reverse Proxy on GNS3 VM Not Accessible Externally on Custom Port 60000 #3653
Labels
Comments
gns3@gns3vm:~$ apt show gns3-server
Package: gns3-server
Version: 2.2.50~focal3
Priority: extra
Section: net
Maintainer: GNS3 team <[email protected]>
Bugs: https://github.com/GNS3/gns3-server/issues
Installed-Size: 50.0 MB
Depends: python3, vpcs, ubridge (>= 0.9.14), qemu-system-x86, qemu-kvm, qemu-utils, mtools, cpulimit, libvirt-daemon-system, debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.14), libgcc-s1 (>= 4.2)
Recommends: dynamips, x11vnc, xvfb
Enhances: gns3-iou
Download-Size: 8780 kB
APT-Sources: http://ppa.launchpad.net/gns3/ppa/ubuntu focal/main amd64 Packages
Description: GNS3 server |
|
|
GNS3 uses websockets to get events/notifications from the server. Please try the following NGINX Configuration. |
|
Hey, thanks for the answer, but the problem is accessing the gns3vm outside. Accessing the node from gns3vm has succeeded thanks to your configuration. Laptop --❌--> gnx3vm --✅--> ubuntu node (inside gns3) I’m still encountering a challenge with accessing the GNS3VM from an external source. Could you please provide guidance or suggest any additional configurations for this? I've confirmed that there is no issue with the router and firewall. on my laptop: gns3vm: gns3@gns3vm:~$ netstat -tuln | grep 60000
tcp 0 0 0.0.0.0:60000 0.0.0.0:* LISTEN
tcp6 0 0 :::60000 :::* LISTEN
gns3@gns3vm:~$ nmap -sT -p 1-65535 10.10.10.111
Starting Nmap 7.80 ( https://nmap.org ) at 2024-11-25 02:14 UTC
Nmap scan report for gns3vm (10.10.10.111)
Host is up (0.00022s latency).
Not shown: 65489 closed ports
PORT STATE SERVICE
22/tcp open ssh
3080/tcp open stm_pproc
5300/tcp open hacl-hb
5302/tcp open hacl-cfg
5303/tcp open hacl-probe
5306/tcp open sun-mc-grp
5308/tcp open cfengine
5309/tcp open jprinter
5310/tcp open outlaws
5311/tcp open unknown
5312/tcp open permabit-cs
5313/tcp open rrdp
5314/tcp open opalis-rbt-ipc
5315/tcp open hacl-poll
5316/tcp open hpdevms
5317/tcp open hpdevms
5318/tcp open pkix-cmc
5319/tcp open unknown
5321/tcp open bsfsvr-zn-ssl
5322/tcp open unknown
5323/tcp open unknown
5324/tcp open unknown
5325/tcp open unknown
5326/tcp open unknown
5328/tcp open unknown
5329/tcp open unknown
5331/tcp open unknown
33857/tcp open unknown
35127/tcp open unknown
36443/tcp open m2ap
36783/tcp open unknown
38349/tcp open unknown
39127/tcp open unknown
39565/tcp open unknown
40407/tcp open unknown
40449/tcp open unknown
41175/tcp open unknown
42793/tcp open unknown
43637/tcp open unknown
43933/tcp open unknown
44571/tcp open unknown
44877/tcp open unknown
45379/tcp open unknown
45457/tcp open unknown
46007/tcp open unknown
60000/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 3.66 seconds
gns3@gns3vm:~$ curl -I http://192.168.122.156:80
HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)
Date: Mon, 25 Nov 2024 02:20:13 GMT
Content-Type: text/html
Content-Length: 615
Last-Modified: Sat, 28 Sep 2024 14:22:47 GMT
Connection: keep-alive
ETag: "66f81137-267"
Accept-Ranges: bytes |
|
Has your GNS3 VM 2 network adapters, one host-only and one NAT? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’m encountering an issue with my NGINX reverse proxy setup on a GNS3 VM. The proxy works correctly when tested internally within the VM, but attempts to access it externally from my laptop result in a connection failure. I’ve verified that no additional firewalls are active in my topology. Below are the details of my configuration and the troubleshooting steps I’ve performed so far.
Setup Details:
Environment:
• Host Machine: MacBook (macOS)
• Virtualization: GNS3 VM
GNS3 GUI Details:
NGINX Configuration:
server { listen 60000 default_server; listen [::]:60000 default_server; server_name 10.10.10.111; location / { proxy_pass http://192.168.122.156:80; } }Ubuntu Server (Inside GNS3 via NAT 192.168.122.1) :
• IP Address: 192.168.122.156
• Service: NGINX serving on port 80
Issue Description:
• Internal Testing (Within GNS3 VM):
• Executing the following curl command successfully returns a 200 OK response:
Response:
HTTP/1.1 200 OK Server: nginx/1.24.0 (Ubuntu) Date: Wed, 30 Oct 2024 03:35:39 GMT Content-Type: text/html Content-Length: 615 Last-Modified: Sat, 28 Sep 2024 14:22:47 GMT Connection: keep-alive ETag: "66f81137-267" Accept-Ranges: bytes• External Testing (From Laptop):
• Attempting to access the proxy using the following curl command fails:
Error:
curl: (7) Failed to connect to 10.10.10.111 port 60000 after 23 ms: Couldn't connect to serverDiagnostics Performed:
Output:
● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2024-10-01 01:50:58 UTC; 4 weeks 1 days ago Docs: man:nginx(8) Main PID: 70138 (nginx) Tasks: 9 (limit: 38401) Memory: 7.4M CGroup: /system.slice/nginx.service ├─70138 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; ├─70139 nginx: worker process ├─70140 nginx: worker process ├─70141 nginx: worker process ├─70142 nginx: worker process ├─70143 nginx: worker process ├─70144 nginx: worker process ├─70145 nginx: worker process └─70146 nginx: worker process Warning: journal has been rotated since unit was started, output may be incomplete.sudo netstat -nlp | grep :60000Output:
Output:
Note: Port 60000 is not listed as open.
• UFW:
Output:
• iptables:
Output:
• Note: There are no active firewall rules blocking port 60000, and ufw is inactive.
Additional Information:
• According to netstat, NGINX is listening on port 60000 for both IPv4 (0.0.0.0:60000) and IPv6 (:::60000).
• However, nmap does not list port 60000 as open when scanned from within the VM.
• There are no other firewalls or security groups active in the current network topology that could be blocking access to port 60000.
• The GNS3 VM network settings are correctly configured to allow external access to the specified port.
Questions:
What I’ve Tried:
• Verified that NGINX is running and configured correctly to listen on port 60000.
• Confirmed that ufw is inactive and iptables does not block port 60000.
• Successfully accessed the internal server via curl within the VM.
• Confirmed that the port is listening using netstat.
• Attempted to scan ports with nmap, which did not show port 60000 as open.
• Reviewed the gns3-gui package details to ensure there are no related conflicts or dependencies affecting network configurations.
Looking For:
Advice on potential misconfigurations or overlooked settings that could prevent external access to the NGINX reverse proxy on a custom port within a GNS3 VM environment. Guidance on additional troubleshooting steps or configurations to resolve this connectivity issue would be highly appreciated.
Thank you in advance for your assistance!
The text was updated successfully, but these errors were encountered: