starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Pulse is not started automatically after reboot #2020

New Issue
Closed
opened 2026-02-05 03:22:43 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 03:22:43 +03:00
Owner
Copy Link

Originally created by @cianiandreadev on GitHub (Nov 17, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Pulse

📂 What was the exact command used to execute the script?

--

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

9.0.15

📝 Provide a clear and concise description of the issue.

Hi all,

I noticed that after rebooting the Pulse LXC container the service is not started automatically and is therefore not reachable to the address.

I usually solve this by logging in the container and executing the following (command took from the install script)

systemctl enable -q --now pulse

Then the service starts and works perfectly.

Not sure why this happens tho.

🔄 Steps to reproduce the issue.

  1. Install pulse
  2. Reboot LXC container (or, as in my case, reboot the proxmox machine with the "start at launch" of the container activated)
  3. Try to login to Pulse webUI
  4. Service not started
  5. Login in to the LXC shell (via proxmox in my case)
  6. Run systemctl enable -q --now pulse
  7. Now the service is reachable

❌ Paste the full error output (if available).

System not reachable from the browser.

🖼️ Additional context (optional).

No response

Originally created by @cianiandreadev on GitHub (Nov 17, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Pulse ### 📂 What was the exact command used to execute the script? -- ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? 9.0.15 ### 📝 Provide a clear and concise description of the issue. Hi all, I noticed that after rebooting the Pulse LXC container the service is not started automatically and is therefore not reachable to the address. I usually solve this by logging in the container and executing the following (command took from the install script) ```sh systemctl enable -q --now pulse ``` Then the service starts and works perfectly. Not sure why this happens tho. ### 🔄 Steps to reproduce the issue. 1. Install pulse 2. Reboot LXC container (or, as in my case, reboot the proxmox machine with the "start at launch" of the container activated) 3. Try to login to Pulse webUI 4. Service not started 5. Login in to the LXC shell (via proxmox in my case) 6. Run `systemctl enable -q --now pulse` 7. Now the service is reachable ### ❌ Paste the full error output (if available). System not reachable from the browser. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:22:43 +03:00
OVERLORD commented 2026-02-05 03:22:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 17, 2025):

Are you sure, that u use our script and not the script from pulse?

44fbd31eb7/install/pulse-install.sh (L59)

I cannot reproduce it. Shutdown an new Created Container and started. Maybe its an issue for Pulse directly, Not for us. Report it there please.

@MickLesk commented on GitHub (Nov 17, 2025): Are you sure, that u use our script and not the script from pulse? https://github.com/community-scripts/ProxmoxVE/blob/44fbd31eb77e07630eb7cb3654d709075b3b7aa5/install/pulse-install.sh#L59 I cannot reproduce it. Shutdown an new Created Container and started. Maybe its an issue for Pulse directly, Not for us. Report it there please.
OVERLORD commented 2026-02-05 03:22:52 +03:00
Author
Owner
Copy Link

@cianiandreadev commented on GitHub (Nov 18, 2025):

Hi,

Yes, I'm sure I did run using the community script (I leave the tag "community script" when it is created with that).

Ok, since this issue will remain here eventually others can comment if more have this issue.

Thanks for now.

@cianiandreadev commented on GitHub (Nov 18, 2025): Hi, Yes, I'm sure I did run using the community script (I leave the tag "community script" when it is created with that). Ok, since this issue will remain here eventually others can comment if more have this issue. Thanks for now.
OVERLORD commented 2026-02-05 03:22:55 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 18, 2025):

Maybe we Ping @rcourtman directly. Do you have an Idea? Or ever heard this issue?

@MickLesk commented on GitHub (Nov 18, 2025): Maybe we Ping @rcourtman directly. Do you have an Idea? Or ever heard this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2020
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?