You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When proxying the unlighthouse frontend it will try to access the API and websocket routes using the localhost:port url still as this is still the url it is originally hosted on, causing issues as described in: indykoning/unlighthouse-docker#1
Suggested solution
I think the best solution would be to use placeholders for the url in the payload.js and replace these with the window.location.origin so it will use the url you accessed the frontend with.
Alternative
An alternative is given in the respective issue by overwriting all the urls with that of the url you want
Clear and concise description of the problem
When proxying the unlighthouse frontend it will try to access the API and websocket routes using the localhost:port url still as this is still the url it is originally hosted on, causing issues as described in: indykoning/unlighthouse-docker#1
Suggested solution
I think the best solution would be to use placeholders for the url in the
payload.js
and replace these with thewindow.location.origin
so it will use the url you accessed the frontend with.Alternative
An alternative is given in the respective issue by overwriting all the urls with that of the url you want
however this does not work if you can access the same unlighthouse instance from different urls
Additional context
No response
The text was updated successfully, but these errors were encountered: