starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #6833] Pulse v4.3.2+ #1456

New issue

Closed

opened 2026-02-26 12:48:58 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 12:48:58 +03:00

Owner

Originally created by @vhsdream on GitHub (Aug 14, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6833

Originally assigned to: @vhsdream on GitHub.

✅ 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?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

OK so... the binary path has once again moved... back to /opt/pulse/bin. I'll update the script again shortly. And then go touch some grass as the kids say.

@rcourtman please I beg you - my brain can't take any more!

🔄 Steps to reproduce the issue.

N/A

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

No response

Originally created by @vhsdream on GitHub (Aug 14, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6833 Originally assigned to: @vhsdream on GitHub. ### ✅ 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? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. OK so... the binary path has once again moved... back to `/opt/pulse/bin`. I'll update the script again shortly. And then go touch some grass as the kids say. @rcourtman please I beg you - my brain can't take any more! ### 🔄 Steps to reproduce the issue. N/A ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:48:58 +03:00

closed this issue
added the
external

update script
labels

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@tremor021 commented on GitHub (Aug 14, 2025):

@vhsdream @rcourtman whats the deal with all these binary path changes?

@tremor021 commented on GitHub (Aug 14, 2025): @vhsdream @rcourtman whats the deal with all these binary path changes?

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

The deal is that I am too quick to react! If I would just chill a little bit, then maybe I wouldn't have had to change anything.

But also, for a few versions the binary path was /opt/pulse/, then /opt/pulse/bin, and then back again and once more. I do believe that things have been standardised and smoothed out now, and that /opt/pulse/bin is where the path will remain; waiting on @rcourtman to confirm 😄

@vhsdream commented on GitHub (Aug 14, 2025): The deal is that I am too quick to react! If I would just chill a little bit, then maybe I wouldn't have had to change anything. But also, for a few versions the binary path was `/opt/pulse/`, then `/opt/pulse/bin`, and then back again and once more. I do believe that things have been standardised and smoothed out now, and that `/opt/pulse/bin` is where the path will remain; waiting on @rcourtman to confirm 😄

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@MickLesk commented on GitHub (Aug 14, 2025):

Switched the path more than a crooked CEO changes accountants. 😄

@MickLesk commented on GitHub (Aug 14, 2025): Switched the path more than a crooked CEO changes accountants. :smile:

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

Well, testing the new version updates just fine, but then there's a login screen and I never set up an account. So, that's going to need some figuring out.

EDIT: The login screen was there for me because I had an API key set in the service file. Removing that allows access to the WebUI.

Then there is the Security setup page. Upon setting that up, it gives you an autogenerated admin pass and a new API key.

However, in /etc/pulse there is a security-override.conf file which is created at the same time, but it has a completely different API key, and maybe a different password (it's encrypted).

@vhsdream commented on GitHub (Aug 14, 2025): Well, testing the new version updates just fine, but then there's a login screen and I never set up an account. So, that's going to need some figuring out. EDIT: The login screen was there for me because I had an API key set in the service file. Removing that allows access to the WebUI. Then there is the Security setup page. Upon setting that up, it gives you an autogenerated admin pass and a new API key. However, in `/etc/pulse` there is a `security-override.conf` file which is created at the same time, but it has a completely different API key, and maybe a different password (it's encrypted).

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

The new security feature runs a shell script in the background to attempt to insert env vars as an override to the pulse-backend service (ours is just called pulse), and since the app is running as the pulse user it uses sudo which fails because the pulse user is not in the sudo group. Not to mention that I removed shell access.

@MickLesk if you don't object, I'm going to roll our own way of setting this up, bypassing the UI method. We'll generate the username, password and API key and set it up in the systemd service file so this step taken care of automatically.

I'm a bit concerned this may be a breaking change since the various settings in /etc/pulse are encrypted, but I will test and figure it out.

@vhsdream commented on GitHub (Aug 14, 2025): The new security feature runs a shell script in the background to attempt to insert env vars as an override to the `pulse-backend` service (ours is just called `pulse`), and since the app is running as the pulse user it uses `sudo` which fails because the `pulse` user is not in the `sudo` group. Not to mention that I removed shell access. @MickLesk if you don't object, I'm going to roll our own way of setting this up, bypassing the UI method. We'll generate the username, password and API key and set it up in the systemd service file so this step taken care of automatically. I'm a bit concerned this may be a breaking change since the various settings in `/etc/pulse` are encrypted, but I will test and figure it out.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@rcourtman commented on GitHub (Aug 14, 2025):

hey @vhsdream, v4.3.7 addresses all the issues you reported:

service name auto-detection (pulse vs pulse-backend)
no more sudo attempts for non-root users
skips security setup if API_TOKEN already configured
binary path confirmed at /opt/pulse/bin/pulse

tested on actual proxmoxve container and works without any workarounds. sorry for all the chaos with the constant changes

@rcourtman commented on GitHub (Aug 14, 2025): hey @vhsdream, v4.3.7 addresses all the issues you reported: - service name auto-detection (pulse vs pulse-backend) - no more sudo attempts for non-root users - skips security setup if API_TOKEN already configured - binary path confirmed at /opt/pulse/bin/pulse tested on actual proxmoxve container and works without any workarounds. sorry for all the chaos with the constant changes

kerem referenced this issue

2026-02-26 13:32:41 +03:00

[PR #1456] [MERGED] feat: allow adding SSH authorized key for root (advanced settings) by @dsiebel #3181

kerem referenced this issue

2026-02-26 13:32:46 +03:00

[PR #1502] [MERGED] [core] build.func&install.func: Fix ssh keynot added error #3207

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/ProxmoxVE#1456

No description provided.

Rows
Columns