Closed azenkov closed 11 months ago
channel.json
is served from the main server with some configuration. Is your server able to start without errors?
from which server? I am using nginx to server the panel. I dont see where channel.json would come from
To be clear, you are hosting tgstation-server right? Which is the main server this client is for.
Yes. I do. But if I understand correctly it just sends a redirect to the panel if there is no API headers?
Yes, the panel should be being hosted under /app
if you have it enabled.
You should be able to view channel.json
by navigating to /app/channel.json
. Are you able to do that?
What version of TGS are you using for reference?
/app/channel.json gives me 404. And I dont see such file in the /dist folder. Is this something TSG is supposed to generate? Im on 5.16
It's an API endpoint hosted by TGS itself, yes. Do you have ControlPanel:Enable
set to true in your config?
If yes, please upload your TGS log files.
tgs_logs_config.zip Here are the logs and config files.
Make sure the X-Webpanel-Fetch-Channel header is proxied
Wouldn't nginx proxy all headers?
Is your TGS hosted at the root of your site? i.e. xxx.yyy.zzz/app
?
The linked PR above is a TGS release I'm pushing with some additional logging. Hopefully, it will help diagnose the issue here.
Is your TGS hosted at the root of your site? i.e.
xxx.yyy.zzz/app
?
yes
Okay, hopefully this logging reveals more. I'll let you know when the update is out
On Fri, Sept 29, 2023, 6:47 p.m. Anton Zenkov @.***> wrote:
Is your TGS hosted at the root of your site? i.e. xxx.yyy.zzz/app?
yes
— Reply to this email directly, view it on GitHub https://github.com/tgstation/tgstation-server-webpanel/issues/152#issuecomment-1741559493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6LA6RP37NLZGEV6ZQFILTX45FZBANCNFSM6AAAAAA5FIPFAY . You are receiving this because you commented.Message ID: @.***>
It's out now, try updating and attempting to load the control panel and then send me the logs.
Also, can you set the MicrosoftLogLevel config to Warning please? It's very spammy and makes decoding the logs harder than it needs to.
tgs-20231001.log here is it. To make it work I had to put a workaround in nginx config: location /app/channel.json { proxy_pass http://127.0.0.1:5000; break; }
I don't see any control panel logs in the new version, it looks like you turned down both LogLevel
and MicrosoftLogLevel
. If it's working now though I suppose this is dealt with.
Sorry. I still don't understand how I can configure tgs panel to be hosted on a URL different from /app. It seems like /app is hardcoded. Can someone plase explain me.
Yes, it is hard coded. Not meant to be changed
On Sun, Oct 1, 2023, 12:58 a.m. Anton Zenkov @.***> wrote:
Sorry. I still don't understand how I can configure tgs panel to be hosted on a URL different from /app. It seems like /app is hardcoded. Can someone plase explain me.
— Reply to this email directly, view it on GitHub https://github.com/tgstation/tgstation-server-webpanel/issues/152#issuecomment-1741958984, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6LA6WQRI5BQOF275A4LQDX5DZ7TANCNFSM6AAAAAA5FIPFAY . You are receiving this because you modified the open/close state.Message ID: @.***>
You can move the entire server to a subpart but the /app suffix must remain
On Sun, Oct 1, 2023, 12:59 a.m. Jordan Dominion @.***> wrote:
Yes, it is hard coded. Not meant to be changed
On Sun, Oct 1, 2023, 12:58 a.m. Anton Zenkov @.***> wrote:
Sorry. I still don't understand how I can configure tgs panel to be hosted on a URL different from /app. It seems like /app is hardcoded. Can someone plase explain me.
— Reply to this email directly, view it on GitHub https://github.com/tgstation/tgstation-server-webpanel/issues/152#issuecomment-1741958984, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6LA6WQRI5BQOF275A4LQDX5DZ7TANCNFSM6AAAAAA5FIPFAY . You are receiving this because you modified the open/close state.Message ID: @.*** com>
This is what I ended up with. Had to rewrite URLS
location = /tgs-panel {
rewrite /tgs-panel / break;
proxy_pass http://127.0.0.1:5000;
}
location ~ ^/tgs-panel/(.*)$ {
rewrite ^/tgs-panel/(.*)$ /$1 break;
proxy_pass http://127.0.0.1:5000;
}
In production mode for some reason index.html is requesting channel.json, doesnt find it and throws an alert about fallback of some sort. Maybe I misconfigured it somehow?