Web GUI is blank - SSH works

gartzea said:
Code: 
root@gartzea:/# arping -b 192.168.0.62
Interface "lo" is not ARPable
Click to expand...

My bad, this needs:

arping -b 192.168.0.62 -I <interface>

You will see the <interface> to fill within the output of:

ip -c a

Something like en0 or enp1s0, next to your IP address (or just post it).

EDIT: The arping ends when you press CTRL+C.
 
Last edited:
esi_y said:
My bad, this needs:

arping -b 192.168.0.62 -I <interface>

You will see the <interface> to fill within the output of:

ip -c a

Something like en0 or enp1s0, next to your IP address (or just post it).

EDIT: The arping ends when you press CTRL+C.
Click to expand...
Once again, no luck! :/

Code: 
root@gartzea:/# ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp0s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether bc:ae:c5:9b:8a:d5 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether bc:ae:c5:9b:8a:d5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.62/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::beae:c5ff:fe9b:8ad5/64 scope link
       valid_lft forever preferred_lft forever
root@gartzea:/# arping -b 192.168.0.62 -I enp0s7
ARPING 192.168.0.62 from 192.168.0.62 enp0s7
^CSent 34 probes (34 broadcast(s))
Received 0 response(s)
root@gartzea:/# arping -b 192.168.0.62 -I vmbr0
ARPING 192.168.0.62 from 192.168.0.62 vmbr0
^CSent 18 probes (18 broadcast(s))
Received 0 response(s)
 
gartzea said:
No luck using Chrome on Android (incognito and otherwise), but the phone app works.
Click to expand...

So at this point, I would literally want to know if tunneling it over SSH as mentioned above would miraculously solve it.

Is this a Windows client you are using? Are you comfortable with the PuTTY setup?
 
esi_y said:
So at this point, I would literally want to know if tunneling it over SSH as mentioned above would miraculously solve it.

Is this a Windows client you are using? Are you comfortable with the PuTTY setup?
Click to expand...

I followed the PuTTY guide you had sent above but it still did not work.
 
gartzea said:
I tried loading google.com as a quick and dirty test and it worked, however, it was very slow to connect.
Click to expand...

Ok, so you set it up correct, but this is all in your local network, when you say slow, do you mean noticeably slow, as in back to the 90s internet? Or just slower than usual?
 
esi_y said:
Ok, so you set it up correct, but this is all in your local network, when you say slow, do you mean noticeably slow, as in back to the 90s internet? Or just slower than usual?
Click to expand...

Noticeably slow, with some elements of the page taking a bit longer to load even.
 
One more thing, the Firefox default for the proxy setup has this - can you remove it, i.e. leave it blank?

Screenshot 2024-10-29 at 18.53.27.png

EDIT: Grr, screenshot is from Chrome, but FF has the same.
 
Last edited:
gartzea said:
I can't find a way of editing the proxy config for localhost, that's how I got it set up on Firefox:

View attachment 76978

EDIT: I found a flag to enable that option, I'll try and get back.
Click to expand...

Yours looks ok, the "No proxy for" ... does not have a filter. So you are saying, you do not get anything loaded with https://localhost:8006/ ... how about https://127.0.0.1:8006 ?

EDIT: Never mind, I am guessing this from memory and apparently it even says that connections are never proxied for localhost in FF. Can you try the same in Chrome? Apologies.
 
Last edited:
esi_y said:
Yours looks ok, the "No proxy for" ... does not have a filter. So you are saying, you do not get anything loaded with https://localhost:8006/ ... how about https://127.0.0.1:8006 ?

EDIT: Never mind, I am guessing this from memory and apparently it even says that connections are never proxied for localhost in FF. Can you try the same in Chrome? Apologies.
Click to expand...

There was a flag in about:config regarding that, which I enabled, allowing localhost to be proxied.

Both localhost and 127.0.0.1 get stuck loading indefinitely now, without even going past the "new tab" page.
 
There's a small issue for me doing this blindly ... I have not PuTTY here nor FF on Windows to test this to be sure this behaves as it should. :)

But since another address loads for you, it is proxied. The strange thing is, this should not be this slow when the proxy is local machine (your PVE host). I wondering why that could be.

Is there a way for you to e.g. use a network setup that is not routed, i.e. only with switch between your PVE host and client?
 
esi_y said:
There's a small issue for me doing this blindly ... I have not PuTTY here nor FF on Windows to test this to be sure this behaves as it should. :)

But since another address loads for you, it is proxied. The strange thing is, this should not be this slow when the proxy is local machine (your PVE host). I wondering why that could be.

Is there a way for you to e.g. use a network setup that is not routed, i.e. only with switch between your PVE host and client?
Click to expand...

I'm using a very basic network setup, with both machines plugged straight into my ISP provided router/modem. I don't have any other network equipment to test it out with, unfortunately.
 
gartzea said:
I'm using a very basic network setup, with both machines plugged straight into my ISP provided router/modem. I don't have any other network equipment to test it out with, unfortunately.
Click to expand...

Does your client machine have an ethernet port? You could do direct connection with two static IPs configured on both ends.
 
What you mentioned above, that e.g. phone app works tells me that small payloads get around just find, i.e. the API works. It's the web app that seems to be mangled on the way to your browser, at least that's my hypothesis.
 
  • Like
Reactions: gartzea
You must log in or register to reply here.
Top Bottom