github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 01:56:43 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #290] [MERGED] Update Bugsink: Add BEHIND_HTTPS_PROXY env var to docker-compose #340

New Issue
Closed
opened 2025-11-22 20:35:46 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:35:46 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/290
Author: @dyd4dsh7
Created: 8/16/2025
Status: ✅ Merged
Merged: 8/23/2025
Merged by: @Siumauricio

Base: main ← Head: main

📝 Commits (1)

  • a57a3e8 Update Bugsink, Add BEHIND_HTTPS_PROXY env var to docker-compose

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 blueprints/bugsink/docker-compose.yml (+1 -0)

📄 Description

Summary

This PR introduces a new environment variable, BEHIND_HTTPS_PROXY, to the Bugsink service in docker-compose.yml.

  • Default value: false
  • Purpose: Allows configuration for deployments running behind an HTTPS proxy.
  • Usage: Set to true when deploying in environments with an SSL-enabled proxy.

Addresses CSRF failures caused by scheme mismatch behind proxies. When not set, deployments may see:

  • CSRF verification failed, request aborted
  • Origin header does not match (deduced) Host: 'https://domain.com/' != 'http://domain.com/' (wrong scheme); fix your proxy's X-Forwarded-Proto and/or the settings SECURE_PROXY_SSL_HEADER/BEHIND_HTTPS_PROXY

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/290 **Author:** [@dyd4dsh7](https://github.com/dyd4dsh7) **Created:** 8/16/2025 **Status:** ✅ Merged **Merged:** 8/23/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`a57a3e8`](https://github.com/Dokploy/templates/commit/a57a3e81df006af005809d316c36f958e7cd8a24) Update Bugsink, Add BEHIND_HTTPS_PROXY env var to docker-compose ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/bugsink/docker-compose.yml` (+1 -0) </details> ### 📄 Description Summary This PR introduces a new environment variable, BEHIND_HTTPS_PROXY, to the Bugsink service in docker-compose.yml. - Default value: false - Purpose: Allows configuration for deployments running behind an HTTPS proxy. - Usage: Set to true when deploying in environments with an SSL-enabled proxy. Addresses CSRF failures caused by scheme mismatch behind proxies. When not set, deployments may see: - CSRF verification failed, request aborted - Origin header does not match (deduced) Host: 'https://domain.com/' != 'http://domain.com/' (wrong scheme); fix your proxy's X-Forwarded-Proto and/or the settings SECURE_PROXY_SSL_HEADER/BEHIND_HTTPS_PROXY --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-22 20:35:46 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#340
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?