Web GUI is blank - SSH works

[esi_y]

root@gartzea:/# arping -b 192.168.0.62
Interface "lo" is not ARPable

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.

 

[gartzea]

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.

Once again, no luck! :/

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)

 

[esi_y]

Once again, no luck! :/

That's actually fine, I was wondering if you do not have an IP conflict, so you do not.

 

[esi_y]

Silly question, have you tried to load the web interface on another device, even just e.g. phone?

 

[gartzea]

Silly question, have you tried to load the web interface on another device, even just e.g. phone?

No luck using Chrome on Android (incognito and otherwise), but the phone app works.

 

[esi_y]

No luck using Chrome on Android (incognito and otherwise), but the phone app works.

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?

 

[gartzea]

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?

I followed the PuTTY guide you had sent above but it still did not work.

 

[esi_y]

I followed the PuTTY guide you had sent above but it still did not work.

Oh you are fast, but if you followed it and you had the SOCKS in Firefox, did you try to load: https://localhost:8006 ?

 

[gartzea]

Oh you are fast, but if you followed it and you had the SOCKS in Firefox, did you try to load: https://localhost:8006 ?

I tried accessing it through 192.168.0.62:8006 at first, but https://localhost:8006/ gave me this:



I tried loading google.com as a quick and dirty test and it worked, however, it was very slow to connect.

 

[esi_y]

I tried loading google.com as a quick and dirty test and it worked, however, it was very slow to connect.

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?

 

[gartzea]

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?

Noticeably slow, with some elements of the page taking a bit longer to load even.

 

[esi_y]

One more thing, the Firefox default for the proxy setup has this - can you remove it, i.e. leave it blank?



EDIT: Grr, screenshot is from Chrome, but FF has the same.

 

[gartzea]

One more thing, the Firefox default for the proxy setup has this - can you remove it, i.e. leave it blank?

View attachment 76977

I can't find a way of editing the proxy config for localhost, that's how I got it set up on Firefox:



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

 

[esi_y]

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.

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.

 

[gartzea]

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.

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.

 

[esi_y]

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?

 

[gartzea]

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?

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.

 

[esi_y]

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.

Does your client machine have an ethernet port? You could do direct connection with two static IPs configured on both ends.

 

[esi_y]

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.

 

[gartzea]

Does your client machine have an ethernet port? You could do direct connection with two static IPs configured on both ends.

It does. Would you have a guide to doing that so I can test it, please?