F5F Stay Refreshed Hardware Desktop Connection issue with the local server interface.

Connection issue with the local server interface.

Connection issue with the local server interface.

Pages (2): 1 2 Next
M
m4xesh3pard
Member
177
12-27-2016, 05:26 AM
#1
Hi everyone, I've just begun setting up a home server using Proxmox and encountered some issues. The machine is installed and running correctly on my router, which shows up in the device list. I can access the Proxmox web interface from my mobile browser without problems. However, when trying to connect from my desktop via Chrome, Edge, or Firefox, I keep seeing an "unable to connect" error. I've tried disabling the Windows firewall and refreshing the page, but it doesn't help. I'm unsure if the problem lies with my browsers or my Windows configuration. Any suggestions would be greatly appreciated. Thanks.
M
m4xesh3pard
12-27-2016, 05:26 AM #1

Hi everyone, I've just begun setting up a home server using Proxmox and encountered some issues. The machine is installed and running correctly on my router, which shows up in the device list. I can access the Proxmox web interface from my mobile browser without problems. However, when trying to connect from my desktop via Chrome, Edge, or Firefox, I keep seeing an "unable to connect" error. I've tried disabling the Windows firewall and refreshing the page, but it doesn't help. I'm unsure if the problem lies with my browsers or my Windows configuration. Any suggestions would be greatly appreciated. Thanks.

S
Spectrexis
Junior Member
45
01-02-2017, 02:03 AM
#2
Consider using a Chrome-based browser instead of Firefox—it might resolve your problem. The error displayed in Chrome appears differently compared to Firefox. And yes, the page after "IP" looks fine in Firefox.
S
Spectrexis
01-02-2017, 02:03 AM #2

Consider using a Chrome-based browser instead of Firefox—it might resolve your problem. The error displayed in Chrome appears differently compared to Firefox. And yes, the page after "IP" looks fine in Firefox.

K
KeyLimeCat
Member
55
01-02-2017, 06:53 AM
#3
I've tested on Chrome, Edge, and Firefox on desktop. The same problem appears everywhere. It functions normally on my mobile browser, which runs on a Firefox-based system. I believe the issue is specific to Windows. Sometimes the page loads but then stops responding after interaction. Refreshing it doesn't restore functionality. It seems the app only becomes aware of the problem once I try to use it.
K
KeyLimeCat
01-02-2017, 06:53 AM #3

I've tested on Chrome, Edge, and Firefox on desktop. The same problem appears everywhere. It functions normally on my mobile browser, which runs on a Firefox-based system. I believe the issue is specific to Windows. Sometimes the page loads but then stops responding after interaction. Refreshing it doesn't restore functionality. It seems the app only becomes aware of the problem once I try to use it.

B
BanjoTheBear
Member
68
01-06-2017, 09:29 PM
#4
Check the inspect element, as the device toggle could indicate a website issue on desktop sizes
B
BanjoTheBear
01-06-2017, 09:29 PM #4

Check the inspect element, as the device toggle could indicate a website issue on desktop sizes

B
BlaizenBoy
Member
157
01-06-2017, 11:14 PM
#5
The functionality remains intact even when accessing the desktop version through a mobile browser.
B
BlaizenBoy
01-06-2017, 11:14 PM #5

The functionality remains intact even when accessing the desktop version through a mobile browser.

S
Stealthycat75
Member
74
01-09-2017, 05:47 PM
#6
It seems like you're pointing out a possible issue with Windows not functioning properly. It could be due to using Ethernet on the PC while Wi-Fi is active on your phone.
S
Stealthycat75
01-09-2017, 05:47 PM #6

It seems like you're pointing out a possible issue with Windows not functioning properly. It could be due to using Ethernet on the PC while Wi-Fi is active on your phone.

J
Joshiii
Junior Member
17
01-11-2017, 04:41 PM
#7
You're connecting via WiFi on your phone and Ethernet on your computer. The server is also linked through Ethernet straight to the modem or router, just like your desktop.
J
Joshiii
01-11-2017, 04:41 PM #7

You're connecting via WiFi on your phone and Ethernet on your computer. The server is also linked through Ethernet straight to the modem or router, just like your desktop.

Z
Zerstouerneun
Member
186
01-17-2017, 01:33 AM
#8
It seems your device might be using an unusual switch, but you could test connecting a PC via Wi-Fi instead.
Z
Zerstouerneun
01-17-2017, 01:33 AM #8

It seems your device might be using an unusual switch, but you could test connecting a PC via Wi-Fi instead.

1
62
01-17-2017, 07:42 AM
#9
I was able to handle it. I’ll proceed with the update then. Right now I just sent a ping from the PC via the command prompt, and everything is functioning properly.
1
101miniongamer
01-17-2017, 07:42 AM #9

I was able to handle it. I’ll proceed with the update then. Right now I just sent a ping from the PC via the command prompt, and everything is functioning properly.

O
OnlyDaniel
Junior Member
10
01-19-2017, 09:11 PM
#10
I attempted to reach the webUI via my laptop using WiFi, but the experience was much worse. Connecting to the server is also problematic. On the laptop, I can't even link to my router as easily as on my desktop. When I send a ping to my router or server from the laptop, it consistently returns a "general failure." Once I connect my PC to the same WiFi network, basic functions work fine, including accessing the router. However, accessing the server remains impossible despite the general connectivity working.
O
OnlyDaniel
01-19-2017, 09:11 PM #10

I attempted to reach the webUI via my laptop using WiFi, but the experience was much worse. Connecting to the server is also problematic. On the laptop, I can't even link to my router as easily as on my desktop. When I send a ping to my router or server from the laptop, it consistently returns a "general failure." Once I connect my PC to the same WiFi network, basic functions work fine, including accessing the router. However, accessing the server remains impossible despite the general connectivity working.

Pages (2): 1 2 Next