[SOLVED] can't access proxmox web GUI

I must point out - how are you connected to the host? I assume via ssh, but what perturbs me is, maybe you are in your router on that address at 192.168.0.64 ??!! How did you connect via ssh? Maybe you used the named address? IDK.
 
I was doing it with ssh root@192.168.0.64 ,

and actually i just got the gui working looking throw a different thread that was linked in this thread,

G

[SOLVED] Thread 'Cannot Access Web Interface'

I installed Proxmox on 3 new server and all the procedure from the iso went ok. I configured cluster and tested it, all work like a charm.
Now, after a reboot I cannot access to web interface from any server: login to ssh its ok but from web interface (tested in many browser) always return connection refued.
If I try from ssh console to connect with curl or wget I take this:
root@rvs1:/etc/pve# curl https://localhost:8006 -k | grep title
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent...

i just did :

Code: 
mkdir -p /var/lib/pveproxy && touch /var/lib/pveproxy/access.log
then

Code: 
chmod -R 0777 /var/log

then i could access it

i will make sure to change anything else that is asked for in this

F

[SOLVED] Post in thread 'Cannot Access Web Interface'

Hi, sorry for reopening this but I ran into very similar issue and thanks to this thread managed to resolve it. I am still going to post this just in case someone makes the same mistakes as me (or more likely in case I make the same mistake again :) )

I have just installed Proxmox for the first time, fiddled with it and all worked great. I've been uploading ISOs through the web interface until it stopped working, I didn't think much of it so I continued uploading ISOs through SFTP, creating VMs, all was great, until at one point when I was shutting down a VM I got a message along the...
  • Like

i don't think it solves all the issues i was having like the no connection, still can't
Code: 
root@StamPointsRecords:~# ping 1.1.1.1
ping: connect: Network is unreachable

but at least i have the web gui now
 
gfngfn256 said:
You need to make the changes, I've written above.
Click to expand...
thank you so much for all the help it seems to have worked, I made all the changes you told me to do so now it's on 192.168.0.74

Code: 
root@StamPointsRecords:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 192.168.0.74 icmp_seq=1 Destination Host Unreachable
From 192.168.0.74 icmp_seq=2 Destination Host Unreachable
From 192.168.0.74 icmp_seq=3 Destination Host Unreachable
From 192.168.0.74 icmp_seq=4 Destination Host Unreachable
From 192.168.0.74 icmp_seq=5 Destination Host Unreachable
From 192.168.0.74 icmp_seq=6 Destination Host Unreachable
From 192.168.0.74 icmp_seq=7 Destination Host Unreachable
From 192.168.0.74 icmp_seq=8 Destination Host Unreachable
From 192.168.0.74 icmp_seq=9 Destination Host Unreachable
^C
--- 1.1.1.1 ping statistics ---
11 packets transmitted, 0 received, +9 errors, 100% packet loss, time 10244ms
pipe 4
root@StamPointsRecords:~#

well it's saying 0 received but that is different from before and I assume it is working now
 
Are you sure 192.168.0.74 is available & not already used on your NW?
Are you sure your 192.168.0.xxx NW has/uses a /24 mask?
Can you see that 192.168.0.74 listed on your router & how?
 
i can see what is being used with this -> nmap -sP 192.168.0.1/24 :
Code: 
root@StamPointsRecords:~# nmap -sP 192.168.0.1/24
Starting Nmap 7.93 ( https://nmap.org ) at 2025-02-09 21:03 GMT
Nmap scan report for 192.168.0.1
Host is up (0.00037s latency).
MAC Address: 04:81:9B:8A:42:79 (SKY UK Limited)
Nmap scan report for 192.168.0.4
Host is up (0.059s latency).
MAC Address: 70:97:41:95:C2:EC (Arcadyan)
Nmap scan report for 192.168.0.29
Host is up (0.058s latency).
MAC Address: 3C:55:76:A4:8F:5B (Cloud Network Technology Singapore PTE.)
Nmap scan report for 192.168.0.30
Host is up (0.058s latency).
MAC Address: 1C:98:C1:6C:A4:E4 (Cloud Network Technology Singapore PTE.)
Nmap scan report for 192.168.0.40
Host is up (0.11s latency).
MAC Address: 44:AF:28:35:34:9B (Intel Corporate)
Nmap scan report for 192.168.0.53
Host is up (0.0060s latency).
MAC Address: DC:DA:0C:79:66:00 (Unknown)
Nmap scan report for 192.168.0.111
Host is up (0.000044s latency).
MAC Address: BC:24:11:FE:AD:1F (Unknown)
Nmap scan report for 192.168.0.112
Host is up (0.000073s latency).
MAC Address: BC:24:11:65:FC:4F (Unknown)
Nmap scan report for 192.168.0.113
Host is up (0.00020s latency).
MAC Address: BC:24:11:D9:87:30 (Unknown)
Nmap scan report for 192.168.0.114
Host is up (0.00020s latency).
MAC Address: BC:24:11:D9:EE:8C (Unknown)
Nmap scan report for 192.168.0.115
Host is up (0.000033s latency).
MAC Address: BC:24:11:67:DF:97 (Unknown)
Nmap scan report for 192.168.0.117
Host is up (0.000077s latency).
MAC Address: BC:24:11:DD:52:7A (Unknown)
Nmap scan report for 192.168.0.118
Host is up (0.067s latency).
MAC Address: FA:6C:75:AE:10:A1 (Unknown)
Nmap scan report for StamPointsRecords.server (192.168.0.74)
Host is up.
Nmap done: 256 IP addresses (14 hosts up) scanned in 28.16 seconds
root@StamPointsRecords:~#

and

cat /etc/hosts gives :


Code: 
root@StamPointsRecords:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.74 StamPointsRecords.server StamPointsRecords

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@StamPointsRecords:~#
 
I changed it but still same result

Code: 
root@StamPointsRecords:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.74 StamPointsRecords.local StamPointsRecords

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
StamPoints said:
iface vmbr0 inet static
address 192.168.0.64/24
gateway 192.168.0.64
bridge-ports eno1
bridge-stp off
bridge-fd 0
Click to expand...
You are using 192.168.0.64 as the gateway/router, but ...
StamPoints said:
Code: 
root@StamPointsRecords:~# nmap -sP 192.168.0.1/24
Starting Nmap 7.93 ( https://nmap.org ) at 2025-02-09 21:03 GMT
Nmap scan report for 192.168.0.1
Host is up (0.00037s latency).
MAC Address: 04:81:9B:8A:42:79 (SKY UK Limited)
Click to expand...
... could it be that 192.168.0.1 is your router/modem instead?
StamPoints said:
Code: 
nameserver 192.168.0.64
Click to expand...
That would explain why you have no internet and no DNS. Try using 192.168.0.1 as the gateway and nameserver.
 
  • Like
Reactions: wbk and dj423
gfngfn256 said:
Although he confirmed earlier in the post that .64 is his router, & he already changed his Proxmox IP to .74, I believe leesteken is right that .1 is the router based on the nmap timings above.
Click to expand...
I don't understand why the VMs can reach the gateway and internet when using the wrong address for the gateway, and therefore also assumed that .64 was correct.
 
Relooking at the nmap output I'm pretty sure the GW is 192.168.0.1, as I already said above based on timings (the .1 is the shortest) but also based on no .64 showing up. Also what is "SKY UK Limited" , looks like a router.

Google search quote:
What is the gateway for sky router?
Type https://192.168.0.1 in a browser address bar and hit enter (When typing the address, ensure you use https and not http). Enter the login in details for the hub.
Click to expand...
 
I restarted the host, and still getting

Code: 
root@StamPointsRecords:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 192.168.0.74 icmp_seq=1 Destination Host Unreachable
From 192.168.0.74 icmp_seq=2 Destination Host Unreachable
From 192.168.0.74 icmp_seq=3 Destination Host Unreachable
From 192.168.0.74 icmp_seq=4 Destination Host Unreachable
From 192.168.0.74 icmp_seq=5 Destination Host Unreachable
From 192.168.0.74 icmp_seq=6 Destination Host Unreachable
From 192.168.0.74 icmp_seq=7 Destination Host Unreachable
From 192.168.0.74 icmp_seq=8 Destination Host Unreachable
From 192.168.0.74 icmp_seq=9 Destination Host Unreachable
^C
--- 1.1.1.1 ping statistics ---
12 packets transmitted, 0 received, +9 errors, 100% packet loss, time 11303ms
pipe 4
root@StamPointsRecords:~#

After seeing all the thread messages I'm not sure what to do
 
After contemplating whether to send my reply or not, I realized you can ignore it if you don't like it ;-)

Reading:
  • your (first) server has been running for a couple of weeks
  • you joined yesterday
  • you don't seem very comfortable yet either using Linux or (formatting helps on) forums
  • you will run a database for your dad's company once you got the server up
am I right to guess you are very much at the start of learning this stuff?

Very good for you! :-)

The kind of troubleshooting you are doing now is very helpful. BUT it is also frustrating not to get anywhere after trying for a weekend.

Contrary to (correct) advice not to throw everything away on the first hiccup, you may consider reinstalling your server from scratch, and implementing the things you have learned on the clean installation. The problems you encounter are very probably the result of a small typo one place or another, maybe a place where more experienced users would never ask you to have a look because it is so obvious that abc has to be xyz (a missing hostname, by accident deleted a file somewhere, installed a reverse proxy that's messing with routing)

Also, Proxmox is a powerful platform; even though the front end looks friendly enough, there is some learning curve involved. If your father is going to rely on this machine for a database, make sure you know how to make regular automated backups (repeat after us : "RAID is not backup") ; also, for experimenting yourself with AI you don't even need a very powerful system; it's only after you know what you want or when you're out of patience (and not out of money) that very powerful hardware is needed.

Good luck and have fun!
 
  • Like
Reactions: dj423
gfngfn256 said:
Have you tried using the gateway of 192.168.0.1 ?
Click to expand...
that worked thank you so much for that , after changing that and a quick reboot
Code: 
root@StamPointsRecords:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=9.50 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=9.09 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=9.33 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=8.54 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=8.53 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=8.45 ms
^C
--- 1.1.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 8.447/8.905/9.504/0.419 ms
 
  • Like
Reactions: dj423
StamPoints said:
that worked thank you so much for that , after changing that and a quick reboot
Click to expand...

Happy that worked - I asked you numerous posts ago if you were sure of the Gateway, but you ignored/insisted the request. You would have saved a lot of time & effort.


Make sure that address on the second line also reads 192.168.0.1:
Code: 
cat /etc/resolv.conf
search local
nameserver 192.168.0.1


I'm happy you have got it all working - but may I suggest you familiarize yourself with Proxmox & NW in particular before building any complex systems that you & others comes to rely on. Proxmox has a learning curve, but you can master it, if you pay attention to details - slowly!

Anyway now that you have got it working - maybe mark this thread as Solved. At the top of the thread, choose the Edit thread button, then from the (no prefix) dropdown choose Solved.

Happy Proxmoxing.
 
  • Like
Reactions: dj423, wbk and leesteken
You must log in or register to reply here.
Top Bottom