Repository navigation
Using a web proxy for the Server GUI #52
Replies: 3 comments 6 replies
|
The reason your admin ui might not be working is because better-auth requires the protocols to match between the admin ui and the api. So you have to expose both the server/api as well as the admin ui so that both are HTTPS. What I have been recommending to people is to just expose 3 separate subdomains to make it easiest (you already have two out of the three) So you could just set up
Here is my NPM config for
|
|
It can be a lot of work getting all this stuff exposed to the web for remote use, and a few people have complained that its too complicated. Which is why I started building a simpler solution, and I haven't announced it yet because NPM + cloudflare tunnel or tailscale are perfectly viable solutions.
Basically signing up at https://airwave.software will allow you to bind your local server to a subdomain issued by airwave.software and allow you to tunnel everything through that really easily. It works perfectly, just no need for it yet since most people trying out airwave are enthusiasts. That domain, airwave.software essentially takes on the burden of doing the relay/tunneling for you so that you can easily access your server/api/admin-ui/tv-web all from one place. If you're ever interested, I do need people to test it out! |




Uh oh!
There was an error while loading. Please reload this page.
I'm trying to use Nginx Proxy Manager to put the web GUI behind an https FQDN. I tried adding the domain as the WEB_PUBLIC_URL or as EXTRA_CORS_ORIGINS but I get the same error no matter where I put it:
Something went wrong!
NetworkError when attempting to fetch resource.
It works for the TV_WEB_PUBLIC_URL using https and a FQDN. Does the proxy need to provide additional information or do I need to add the IP of the proxy to the EXTRA_CORS_ORIGINS variable?
All reactions