[GH-ISSUE #8] Possible bugs or user error #120

New issue

Closed

opened 2026-03-13 17:12:14 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 17:12:14 +03:00

Owner

Originally created by @xeonzen on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/8

From a UI look and feel perspective, I just have to say this is pretty awesome and definitely gives that VCenter type of experience. Great job on that.

There are some issues that I ran into that make it unusable to me in the current state, hoping they get sorted out or if its user error, guidance would be helpful.

Deployment details:
I installed Proxcenter manually using the docker compose file in your repo. It was installed on my truenas server via a custom docker app and I modified the docker compose files network config to utilize macvlan, so that i could set a static ip address for the container.

Issues that I ran into:

After deployment i was able to access Proxcenter via the set static ip using port 3000 and it allowed me to create the initial user. Unfortunately, it would not let me login with that user. To resolve this, I needed to add a .env file to the folder with the docker compose file and adding a FQDN for https. I added it as an entry on my npm reverse proxy and then also to my dns server. Once done, i used the FQDN via https to access Proxcenter and was able to log in with the username and password that I created on initial launch.
I added my Proxmox cluster without ssh enabled at first, everything shows in inventory but when trying to console into the vm or a pve host, it just hangs on a black screen saying reconnect.

To troubleshoot, I tried deleting the cluster from Proxcenter and this caused proxcenter to hang and not delete the cluster. Ignoring the old entry, I tried readding the same cluster with a different name and enabled ssh. This caused Proxcenter to throw error stating connection failure when trying to look at any inventory items. As a final troubleshooting task, I deleted the Proxcenter docker container, image and storage and redeployed fresh. Once it was back up and I was logged in, I readded the cluster again with ssh enabled. This allowed Proxcenter to show more information in regards to updates for PVE hosts but I was still not able to console/shell into VM's or pve hosts.

The interface overall is half in english and half in what I assume is french. The UI language control doesn't fix this when set to english.
Random json errors with no context, when adding proxmox nodes. It seems If all fields aren't filled in perfectly on the first try, it will throw a json trim error, with no indication on what field needs to be fixed. The only way around this is to close the window and start over.

With the issues above, I also found that the docker logs file for the container doesn't really help much to tell you what might be failing or any errors that the container is running into. Any time that i've checked the docker log for proxcenter, all I see is the inital deployment output that says that ends with it saying it was ready in x seconds.

Please let me know if there is another place that I should be looking for the log files, and i'd be happy to provide them.

On a side note, there are a lot of features are blocked by the enterprise license paywall that I'd love to use in my home lab. Any plans on expanding the feature set of the community edition or implementing a cheaper personal license schema, that includes access to enterprise features, in the future? I have a 6 node proxmox cluster at home, $235 (USD)/ per node/ per year is a bit steep. longshot but just thought i'd ask.

Originally created by @xeonzen on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/8 From a UI look and feel perspective, I just have to say this is pretty awesome and definitely gives that VCenter type of experience. Great job on that. There are some issues that I ran into that make it unusable to me in the current state, hoping they get sorted out or if its user error, guidance would be helpful. Deployment details: I installed Proxcenter manually using the docker compose file in your repo. It was installed on my truenas server via a custom docker app and I modified the docker compose files network config to utilize macvlan, so that i could set a static ip address for the container. Issues that I ran into: 1. After deployment i was able to access Proxcenter via the set static ip using port 3000 and it allowed me to create the initial user. Unfortunately, it would not let me login with that user. To resolve this, I needed to add a .env file to the folder with the docker compose file and adding a FQDN for https. I added it as an entry on my npm reverse proxy and then also to my dns server. Once done, i used the FQDN via https to access Proxcenter and was able to log in with the username and password that I created on initial launch. 2. I added my Proxmox cluster without ssh enabled at first, everything shows in inventory but when trying to console into the vm or a pve host, it just hangs on a black screen saying reconnect. - To troubleshoot, I tried deleting the cluster from Proxcenter and this caused proxcenter to hang and not delete the cluster. Ignoring the old entry, I tried readding the same cluster with a different name and enabled ssh. This caused Proxcenter to throw error stating connection failure when trying to look at any inventory items. As a final troubleshooting task, I deleted the Proxcenter docker container, image and storage and redeployed fresh. Once it was back up and I was logged in, I readded the cluster again with ssh enabled. This allowed Proxcenter to show more information in regards to updates for PVE hosts but I was still not able to console/shell into VM's or pve hosts. 3. The interface overall is half in english and half in what I assume is french. The UI language control doesn't fix this when set to english. 4. Random json errors with no context, when adding proxmox nodes. It seems If all fields aren't filled in perfectly on the first try, it will throw a json trim error, with no indication on what field needs to be fixed. The only way around this is to close the window and start over. With the issues above, I also found that the docker logs file for the container doesn't really help much to tell you what might be failing or any errors that the container is running into. Any time that i've checked the docker log for proxcenter, all I see is the inital deployment output that says that ends with it saying it was ready in x seconds. Please let me know if there is another place that I should be looking for the log files, and i'd be happy to provide them. On a side note, there are a lot of features are blocked by the enterprise license paywall that I'd love to use in my home lab. Any plans on expanding the feature set of the community edition or implementing a cheaper personal license schema, that includes access to enterprise features, in the future? I have a 6 node proxmox cluster at home, $235 (USD)/ per node/ per year is a bit steep. longshot but just thought i'd ask.

kerem closed this issue

2026-03-13 17:12:19 +03:00

kerem commented

2026-03-13 17:12:25 +03:00

Author

Owner

@adminsyspro commented on GitHub (Feb 18, 2026):

Thank you for the detailed feedback — this is really helpful. Here's an update on each point you raised:

NextAuth was automatically setting secure: true on cookies when NEXTAUTH_URL started with https://, which silently prevents login over plain HTTP (browsers refuse to store secure cookies on non-HTTPS connections). We now explicitly control cookie security based on the protocol. (commit 6a8c245)

2. Console black screen / reconnect : Fixed

Several improvements:

Session TTL increased from 8s to 30s to accommodate reverse proxy setups with higher latency (commit 6378095)
WebSocket port detection improved — any port other than 3000 (direct Docker) now correctly routes through the reverse proxy path, which fixes setups behind NPM or nginx on non-standard ports (commit 6378095)
Internal API URL is no longer hardcoded to port 3000, so custom port configurations work correctly (commit 6378095)

3. Interface half English / half French : In progress

This is tracked separately in #7. Many components still have hardcoded French strings instead of using the translation system. This is a larger effort that we're working on.

4. JSON errors when adding nodes : Fixed

Error messages now include specific field details from validation (instead of generic "Invalid input")
Fixed a bug where invalid latitude/longitude values could produce NaN and cause cryptic errors (commit 7916eb8)

5. Docker logs / debugging

The WebSocket proxy already logs connection events. Next.js in production mode is intentionally quiet for performance, but we'll consider adding optional request logging in a future release.

Most fixes are available in the latest Docker image. Could you try again and confirm it's ok on your side please ?

@adminsyspro commented on GitHub (Feb 18, 2026): Thank you for the detailed feedback — this is really helpful. Here's an update on each point you raised: ### 1. Login not working without HTTPS : Fixed NextAuth was automatically setting `secure: true` on cookies when `NEXTAUTH_URL` started with `https://`, which silently prevents login over plain HTTP (browsers refuse to store secure cookies on non-HTTPS connections). We now explicitly control cookie security based on the protocol. (commit 6a8c245) ### 2. Console black screen / reconnect : Fixed Several improvements: - **Session TTL** increased from 8s to 30s to accommodate reverse proxy setups with higher latency (commit 6378095) - **WebSocket port detection** improved — any port other than 3000 (direct Docker) now correctly routes through the reverse proxy path, which fixes setups behind NPM or nginx on non-standard ports (commit 6378095) - **Internal API URL** is no longer hardcoded to port 3000, so custom port configurations work correctly (commit 6378095) ### 3. Interface half English / half French : In progress This is tracked separately in #7. Many components still have hardcoded French strings instead of using the translation system. This is a larger effort that we're working on. ### 4. JSON errors when adding nodes : Fixed - Error messages now include **specific field details** from validation (instead of generic "Invalid input") - Fixed a bug where invalid latitude/longitude values could produce `NaN` and cause cryptic errors (commit 7916eb8) ### 5. Docker logs / debugging The WebSocket proxy already logs connection events. Next.js in production mode is intentionally quiet for performance, but we'll consider adding optional request logging in a future release. --- Most fixes are available in the latest Docker image. Could you try again and confirm it's ok on your side please ?

kerem commented

2026-03-13 17:12:30 +03:00

Author

Owner

@adminsyspro commented on GitHub (Feb 18, 2026):

Point 3 (interface half English / half French): This has been fixed in commit 604b00c. We replaced ~290 hardcoded French strings across ~35 UI component files with proper i18n translations, and removed all hardcoded fr-FR date formatting. Switching to English should now show a fully English interface.

Points 1, 2, and 4: We are aware of these issues and will investigate them separately. If you can provide screenshots or logs for the JSON errors (point 4), that would help us reproduce and fix it faster.

@adminsyspro commented on GitHub (Feb 18, 2026): **Point 3 (interface half English / half French):** This has been fixed in commit 604b00c. We replaced ~290 hardcoded French strings across ~35 UI component files with proper i18n translations, and removed all hardcoded `fr-FR` date formatting. Switching to English should now show a fully English interface. **Points 1, 2, and 4:** We are aware of these issues and will investigate them separately. If you can provide screenshots or logs for the JSON errors (point 4), that would help us reproduce and fix it faster.