[GH-ISSUE #74] Install on the PVE host will let PVE web can't access #29

Closed
opened 2026-02-26 17:36:56 +03:00 by kerem · 9 comments
Owner

Originally created by @weili0677 on GitHub (Jul 31, 2023).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-admin/issues/74

Bug type

Other

Component name

No response

What happened?

1、install cv4pve-admin on PVE host
2、open PVE website(8006 port)
3、open cv4pve-admin(5000 port) and login.
4、refresh PVE website will get connect fail error.

If I use another browser will open PVE website success.when I restart browser and only access PVE website it is good.

Expected behavior

fix this bugs.

Relevant log output

No response

Proxmox VE Version

8.0.3

Version (bug)

1.0.0

Version (working)

No response

What browsers are you seeing the problem on?

Chrome, Microsoft Edge

On what operating system are you experiencing the issue?

Windows

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @weili0677 on GitHub (Jul 31, 2023). Original GitHub issue: https://github.com/Corsinvest/cv4pve-admin/issues/74 ### Bug type Other ### Component name _No response_ ### What happened? 1、install cv4pve-admin on PVE host 2、open PVE website(8006 port) 3、open cv4pve-admin(5000 port) and login. 4、refresh PVE website will get connect fail error. If I use another browser will open PVE website success.when I restart browser and only access PVE website it is good. ### Expected behavior fix this bugs. ### Relevant log output _No response_ ### Proxmox VE Version 8.0.3 ### Version (bug) 1.0.0 ### Version (working) _No response_ ### What browsers are you seeing the problem on? Chrome, Microsoft Edge ### On what operating system are you experiencing the issue? Windows ### Pull Request - [ ] I would like to do a Pull Request ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
kerem closed this issue 2026-02-26 17:36:56 +03:00
Author
Owner

@franklupo commented on GitHub (Aug 1, 2023):

could it be a cache problem?

<!-- gh-comment-id:1660709175 --> @franklupo commented on GitHub (Aug 1, 2023): could it be a cache problem?
Author
Owner

@weili0677 commented on GitHub (Aug 2, 2023):

could it be a cache problem?

I don't know. May be because I set the WEB API with linux "root" account?

<!-- gh-comment-id:1661598750 --> @weili0677 commented on GitHub (Aug 2, 2023): > could it be a cache problem? I don't know. May be because I set the WEB API with linux "root" account?
Author
Owner

@kenrmayfield commented on GitHub (Aug 4, 2023):

@weili0677

The Proxmox Connect Fail Error is irrelevant to CV4PVE-Admin.

  1. SSH to Proxmox and type journalctl -f and see if there are Error Messages
  2. Are you using DHCP or Static IP Address for Proxmox.......if Static.....make sure to Reserve the IP Address from the DHCP Range
    if that is where you got the IP Address from
  3. As FrankLupo stated.....Delete Browser Cache or Close the TAB and Open a New One or Close Restart Effected Browser

Setting your Proxmox Account to be the same as your Linux Root Account does not matter either.

<!-- gh-comment-id:1665122818 --> @kenrmayfield commented on GitHub (Aug 4, 2023): @weili0677 The Proxmox Connect Fail Error is irrelevant to CV4PVE-Admin. 1. SSH to Proxmox and type journalctl -f and see if there are Error Messages 2. Are you using DHCP or Static IP Address for Proxmox.......if Static.....make sure to Reserve the IP Address from the DHCP Range if that is where you got the IP Address from 4. **As FrankLupo stated.....Delete Browser Cache or Close the TAB and Open a New One or Close Restart Effected Browser** Setting your Proxmox Account to be the same as your Linux Root Account does not matter either.
Author
Owner

@franklupo commented on GitHub (Aug 11, 2023):

News?

<!-- gh-comment-id:1675113533 --> @franklupo commented on GitHub (Aug 11, 2023): News?
Author
Owner

@weili0677 commented on GitHub (Aug 14, 2023):

@weili0677

The Proxmox Connect Fail Error is irrelevant to CV4PVE-Admin.

  1. SSH to Proxmox and type journalctl -f and see if there are Error Messages
  2. Are you using DHCP or Static IP Address for Proxmox.......if Static.....make sure to Reserve the IP Address from the DHCP Range
    if that is where you got the IP Address from
  3. As FrankLupo stated.....Delete Browser Cache or Close the TAB and Open a New One or Close Restart Effected Browser

Setting your Proxmox Account to be the same as your Linux Root Account does not matter either.

It's not working.

<!-- gh-comment-id:1676714706 --> @weili0677 commented on GitHub (Aug 14, 2023): > @weili0677 > > The Proxmox Connect Fail Error is irrelevant to CV4PVE-Admin. > > 1. SSH to Proxmox and type journalctl -f and see if there are Error Messages > 2. Are you using DHCP or Static IP Address for Proxmox.......if Static.....make sure to Reserve the IP Address from the DHCP Range > if that is where you got the IP Address from > 3. **As FrankLupo stated.....Delete Browser Cache or Close the TAB and Open a New One or Close Restart Effected Browser** > > Setting your Proxmox Account to be the same as your Linux Root Account does not matter either. It's not working.
Author
Owner

@franklupo commented on GitHub (Aug 14, 2023):

can you try to run it outside Proxmox VE in another host?

Also try the new aversion

bets regards

<!-- gh-comment-id:1676792053 --> @franklupo commented on GitHub (Aug 14, 2023): can you try to run it outside Proxmox VE in another host? Also try the new aversion bets regards
Author
Owner

@kenrmayfield commented on GitHub (Aug 14, 2023):

@weili0677

Also what is the Exact Error Message?

<!-- gh-comment-id:1676891543 --> @kenrmayfield commented on GitHub (Aug 14, 2023): @weili0677 Also what is the Exact Error Message?
Author
Owner

@weili0677 commented on GitHub (Aug 14, 2023):

I update to 1.0.1 and it fix this bug.Thank you so much.

<!-- gh-comment-id:1677135534 --> @weili0677 commented on GitHub (Aug 14, 2023): I update to 1.0.1 and it fix this bug.Thank you so much.
Author
Owner

@weili0677 commented on GitHub (Aug 14, 2023):

the service was not fix.I will create new Issues.

<!-- gh-comment-id:1677143426 --> @weili0677 commented on GitHub (Aug 14, 2023): the service was not fix.I will create new Issues.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cv4pve-admin#29
No description provided.