SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Pelican Panel - Apache Mixed Content Error #2324

New Issue
Open
opened 2025-11-20 05:27:29 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:27:29 -05:00
Owner
Copy Link

Originally created by @WoolMagician on GitHub (Nov 15, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Pelican Panel

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

The script as it is sets up Apache as internal webpage server, this causes errors in the Laravel backend used by Pelican when a reverse proxy handling high level HTTPS (Like NPM with Letsencrypt SSL) is put in front of Apache.

🔄 Steps to reproduce the issue.

  • Install Pelican Panel
  • Install Pelican Wings (Node)
  • Follow official setup instructions to get both Panel and Node working.
  • Try to edit server files using the "edit" button.

❌ Paste the full error output (if available).

Mixed Content: The page at 'https:///server/5acb331d/files' was loaded over HTTPS, but requested an insecure resource 'http:///server/5acb331d/files/edit/server.properties'. This request has been blocked; the content must be served over HTTPS.

🖼️ Additional context (optional).

PROPOSED SOLUTION

✅ Switching from Apache to plain NGINX (following Pelican Panel docs for HTTP and not HTTPS!) solved every issue and resulted in better performance overall. Link to config here.

Originally created by @WoolMagician on GitHub (Nov 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Pelican Panel ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pelican-panel.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve) ### 📝 Provide a clear and concise description of the issue. The script as it is sets up Apache as internal webpage server, this causes errors in the Laravel backend used by Pelican when a reverse proxy handling high level HTTPS (Like NPM with Letsencrypt SSL) is put in front of Apache. ### 🔄 Steps to reproduce the issue. - Install Pelican Panel - Install Pelican Wings (Node) - Follow official setup instructions to get both Panel and Node working. - Try to edit server files using the "edit" button. ### ❌ Paste the full error output (if available). Mixed Content: The page at 'https://<DOMAIN>/server/5acb331d/files' was loaded over HTTPS, but requested an insecure resource 'http://<DOMAIN>/server/5acb331d/files/edit/server.properties'. This request has been blocked; the content must be served over HTTPS. ### 🖼️ Additional context (optional). ### PROPOSED SOLUTION ✅ Switching from Apache to plain NGINX (following Pelican Panel docs for HTTP and not HTTPS!) solved every issue and resulted in better performance overall. Link to config [here](https://pelican.dev/docs/panel/webserver-config).
saavagebueno added the not a script issuequestionnice to have labels 2025-11-20 05:27:29 -05:00
saavagebueno commented 2025-11-20 05:27:30 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 15, 2025):

Why are you reporting this as error? This is a user configuration issue. The script configures apache as per official documentation, over HTTP. You want to use HTTPS, so configure it yourself, just look at the documentation

This is not a issue for us.

@tremor021 commented on GitHub (Nov 15, 2025): Why are you reporting this as error? This is a user configuration issue. The script configures apache as per official documentation, over HTTP. You want to use HTTPS, so configure it yourself, just look at the documentation This is not a issue for us.
saavagebueno commented 2025-11-20 05:27:30 -05:00
Author
Owner
Copy Link

@WoolMagician commented on GitHub (Nov 15, 2025):

@tremor021 The reason I'm reporting this is that a lot of people will just set everything up with a reverse proxy/public DNS records for Panel/Wings to work. I don't want to modify the script to allow HTTPS, the NGINX configuration I reported is HTTP and completely equivalent to the current Apache one BUT it works flawlessly.
Using NGINX will just work in any case (also with HTTPS, not restricted to) so it's just a more reliable setup and covers more options for the end user without having to juggle.
I've spend myself a lot of time trying to fix this, and Apache just seems to not be the best option for this service.

@WoolMagician commented on GitHub (Nov 15, 2025): @tremor021 The reason I'm reporting this is that a lot of people will just set everything up with a reverse proxy/public DNS records for Panel/Wings to work. I don't want to modify the script to allow HTTPS, the NGINX configuration I reported is HTTP and completely equivalent to the current Apache one BUT it works flawlessly. Using NGINX will just work in any case (also with HTTPS, not restricted to) so it's just a more reliable setup and covers more options for the end user without having to juggle. I've spend myself a lot of time trying to fix this, and Apache just seems to not be the best option for this service.
saavagebueno commented 2025-11-20 05:27:30 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Nov 15, 2025):

@WoolMagician thank you for your finding, normally this is something that is up to the user, as per the documentation of pelican panel our setup for http (which is default) is working fine, if the user wants HTTPS, that's up to them, though you are right with this being a bit unfortunate.

As we are currently quite busy with pve-local and the debian13 migration, you are free to create a PR and add the correct install for nginx and upgrade steps to safely migrate the userbase to nginx.

@CrazyWolf13 commented on GitHub (Nov 15, 2025): @WoolMagician thank you for your finding, normally this is something that is up to the user, as per the documentation of pelican panel our setup for http (which is default) is working fine, if the user wants HTTPS, that's up to them, though you are right with this being a bit unfortunate. As we are currently quite busy with pve-local and the debian13 migration, you are free to create a PR and add the correct install for nginx and upgrade steps to safely migrate the userbase to nginx.
saavagebueno commented 2025-11-20 05:27:30 -05:00
Author
Owner
Copy Link

@WoolMagician commented on GitHub (Nov 15, 2025):

@CrazyWolf13 Thank you, I'll try to get something working for a PR.

@WoolMagician commented on GitHub (Nov 15, 2025): @CrazyWolf13 Thank you, I'll try to get something working for a PR.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label nice to have not a script issue question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2324
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?