[SOLVED] Problem accessing the server gui

[FlyByWire]

I' realized that I have a strange issue. I normally access the gui via Firefox from my DesktopPC running Windows 11 @ localIP:8006. Today I tried to access from another Windows Laptop. After accepting the risk (certificate issue) I get a connect, but just blank screen. Same thing on my DesktopPC with other browsers (tried chrome and Edge).

From PC & Firefox access is still possible.
iPhone access via safari also working.

I already restarted the node. No change.



Any help appreciated!

 

[sb-jw]

Take a look at the developer console to see what happens. Maybe an ad blocker is active or you would have to delete cache etc., maybe even private tab. If Proxmox is not up to date, maybe update it.

 

[FlyByWire]

developer console

You mean this: https://your.server:8006/api2/json/ ?

delivers:


Proxmox is up-to-date (right now it's still without subscription, if this is important)

 

[sb-jw]

There is significantly more information in the developer console than in your screenshot. Just look through all the tabs and maybe just compare them. Then you can see whether resources are blocked or not.

 

[FlyByWire]

the only maybe helpful I could find is that:


the developer console is also not reachable from other devices. Sorry for being complicated. Thanks for your help!

 

[sb-jw]

The screenshot is anything but helpful, it doesn't show which resources are or are not being loaded, and I don't see any error messages about something that wasn't executed correctly.

If you can't provide the information and my other tips don't help, then I'm out, without information I can't help.

 

[FlyByWire]

I'm sorry. If you could tell me, what to look for, I will do my best to try.
This is the only other information provided on this console (if we are talking about the same thing?)

cache has been cleared and no adblocker

 

[sb-jw]

(if we are talking about the same thing?)

Yes, that's already an excerpt of it. As mentioned, there are also other tabs such as the console or network. The developer tools must remain open and, ideally, reload them with CTRL + F5 so that data appears there.

 

[FlyByWire]

there are also other tabs such as the console or network

Unfortunately not. Again, this console is only reachable from Firefox on DektopPC. I restarted the DesktopPC already. On the DesktopPC not matter how often I press Crtl+F5 no change, no other tabs.

I'm not quite sure if this is important, but on my DesktopPC after entering localIP:8006, the browser adds some code to the IP like this: localIP:8006/#v1:0:18:4:::::::

 

[sb-jw]

Again, this console is only reachable from Firefox on DektopPC.

This is a standard feature in every desktop browser, whether Chrome, Firefox or Edge - it is included everywhere.

I restarted the DesktopPC already. On the DesktopPC not matter how often I press Crtl+F5 no change, no other tabs.

That's illogical, that doesn't make sense. Then your PC or browser is broken and unusable. Make sure your browsers are up to date.

Here is the documentation for a few browsers:
Firefox: https://firefox-source-docs.mozilla.org/devtools-user/ (for example see this: https://firefox-source-docs.mozilla.org/devtools-user/#network-monitor)
Edge: https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/overview
Chrome: https://developer.chrome.com/docs/devtools/open?hl=en

 

[FlyByWire]

So you are talking about the developer tools of the browser? I was thinking of the Proxmox server (localIP:8006/api2/json/)

 

[sb-jw]

developer tools of the browser?

Yes, of course, why should PVE have a problem when it works on other devices? So it doesn't seem logical to me that the PVE should have problems.

I was thinking of the Proxmox server (localIP:8006/api2/json/)

This is the API endpoint, this is not a developer console.

 

[FlyByWire]

I think I've got you now. This is the (working) Firefox console:

and this is chrome output:

 

[FlyByWire]

I'm afraid I made things worse. After clearing the cache at the DesktopPC it's not working there either. Looking on the message from chrome I remember that I tried to integrate a Temp sensor for the CPU to proxmox. Following a guide, some things had to be changed in

/usr/share/pve-manager/js/pvemanagerlib.js

So most likely, even if I think I reverted anything back, I might have made a mistake there.

Is there any way to repair the pvemanager?

 

[FlyByWire]

I was able to repair the pbvemanagerlib.js. Now it's working again.
Thanks for your help! I swear I never touch any of the core files again.