Improvements to URL handling in the webapp allowing for SSL (when behind a proxy) #104296
No reviewers
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#104296
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "william-at-counter/flamenco:main"
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?
Ran into an issue today in which putting flamenco-manager behind a reverse proxy (such as Nginx Proxy Manager) caused web sockets to break if the proxy was providing SSL. This is due to the treatment of URLs in the web app, where the "ws" protocol is always used regardless of whether the site is being accessed through http or https.
I also commented out a block of code that I believe was committed in error since it makes port 8081 inexplicably broken in the release version! 😁
Figured I might as well add a better mechanism for running the dev server while I'm at it.
Using
--mode development
in your vite dev or build commands will instructurls.js
to force port 8080 rather than having to comment/uncomment each time.Thanks, this is a great improvement!
Just one little note, if you could address that then we can land this before 3.5 is released.
@ -3,2 +2,2 @@
// API, for example when using the Vite devserver. Set the API port here.
if (url.port == '8081') {
// When using Vite development mode, access the API on port 8080.
The new comment doesn't explain why this piece of code is there to begin with. Please do keep the explanation that when using Vite in dev mode, the web app runs on a different port than the API.
Done 👍
Putting this here for anyone facing SSL issues coming from search, you can use the following command to patch the
flamenco-3.4-linux-amd64
version of flamenco-manager with an approximate fix (see this Dockerfile)Thanks @William-Gardner so much for this patch... really useful!
I don't think it's a good idea to suggest patching the executable. Better to either build your own executable with a fix backported locally, or wait for the new release.
Thanks!