Home page URLs broken in Dashboard #99

Closed
opened 2025-12-29 14:24:51 +01:00 by adam · 11 comments
Owner

Originally created by @mrg358 on GitHub (Aug 18, 2025).

In latest release v0.17.0 homepage urls in dashboard got injected with 'godoxy' subdomain like my-alias.godoxy.my.domain.com so they do not resolve and became invalid.

Originally created by @mrg358 on GitHub (Aug 18, 2025). In latest release v0.17.0 homepage urls in dashboard got injected with 'godoxy' subdomain like `my-alias.godoxy.my.domain.com` so they do not resolve and became invalid.
adam closed this issue 2025-12-29 14:24:51 +01:00
Author
Owner

@yusing commented on GitHub (Aug 18, 2025):

Thanks, will fix it tonight.

@yusing commented on GitHub (Aug 18, 2025): Thanks, will fix it tonight.
Author
Owner

@yusing commented on GitHub (Aug 18, 2025):

Should be fixed, please pull again. Thanks

@yusing commented on GitHub (Aug 18, 2025): Should be fixed, please pull again. Thanks
Author
Owner

@abjoseph commented on GitHub (Aug 18, 2025):

Should be fixed, please pull again. Thanks

I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get no such route: godoxy.example.net

@abjoseph commented on GitHub (Aug 18, 2025): > Should be fixed, please pull again. Thanks I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get `no such route: godoxy.example.net`
Author
Owner

@mrg358 commented on GitHub (Aug 18, 2025):

Should be fixed, please pull again. Thanks

I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get no such route: godoxy.example.net

Same problem. Latest fix removed the redundant godoxy part but also removed the my subdomain from service-alias.godoxy.my.domain.com.

Now I left with incorrect service-alias.domain.com. Correct setup should be service-alias.my.domain.com.

@mrg358 commented on GitHub (Aug 18, 2025): > > Should be fixed, please pull again. Thanks > > I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get `no such route: godoxy.example.net` Same problem. Latest fix removed the redundant `godoxy` part but also removed the `my` subdomain from `service-alias.godoxy.my.domain.com`. Now I left with incorrect `service-alias.domain.com`. Correct setup should be `service-alias.my.domain.com`.
Author
Owner

@dacagi commented on GitHub (Aug 18, 2025):

Reporting similar behavior in my setup. I have another reverse proxy for my main domain.com, and use Godoxy under a separate subdomain tree *.go.domain.com. This is configured in autocert->domains. I also tried to set the new match_domains field to go.domain.com with no change (would love better docs on this btw).

Before last (<0.17) update, my proxied domains were correctly created as app.go.domain.com and I accessed godoxy at godoxy.go.domain.com. I can still manually access all services with their 'old' app.go.domain.com URL, but links in the dashboard are wrong.

What surprises me, is that this didn't happen for all of them. I have 2 services showing in the dashboard as app.go.domain.com, but the rest of the apps on that same server show up as app.domain.com.

Another strange case. I have filebrowser running on two servers with equivalent compose files. One of them is listed as files1.domain.com, but the second one shows as files2.go.domain.com.

Hope this helps pinpoint root cause and edge cases. Thanks dev!

@dacagi commented on GitHub (Aug 18, 2025): Reporting similar behavior in my setup. I have another reverse proxy for my main `domain.com`, and use Godoxy under a separate subdomain tree `*.go.domain.com`. This is configured in **autocert->domains**. I also tried to set the new **match_domains** field to `go.domain.com` with no change (would love better docs on this btw). Before last (<0.17) update, my proxied domains were correctly created as `app.go.domain.com` and I accessed godoxy at `godoxy.go.domain.com`. **I can still manually access all services with their 'old' `app.go.domain.com` URL, but links in the dashboard are wrong.** What surprises me, is that this didn't happen for all of them. I have 2 services showing in the dashboard as `app.go.domain.com`, but the rest of the apps on that same server show up as `app.domain.com`. Another strange case. I have filebrowser running on two servers with equivalent compose files. One of them is listed as `files1.domain.com`, but the second one shows as `files2.go.domain.com`. Hope this helps pinpoint root cause and edge cases. Thanks dev!
Author
Owner

@yusing commented on GitHub (Aug 18, 2025):

Should be fixed, please pull again. Thanks

I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get no such route: godoxy.example.net

I have made no change except the url and some API stuff though. Not sure why

@yusing commented on GitHub (Aug 18, 2025): > > Should be fixed, please pull again. Thanks > > I just re-pulled the latest, but the fix appears to have removed genuine routes with the sub-domain "godoxy". In my case, the alias for my godoxy web ui is "godoxy" and so now I'm not able load the Frontend app as I get `no such route: godoxy.example.net` I have made no change except the url and some API stuff though. Not sure why
Author
Owner

@yusing commented on GitHub (Aug 18, 2025):

Will check and hopefully fix it tmr

@yusing commented on GitHub (Aug 18, 2025): Will check and hopefully fix it tmr
Author
Owner

@yusing commented on GitHub (Aug 19, 2025):

Hi @dacagi @abjoseph @mrg358 please update to v0.17.2, thanks for reporting the issue

@yusing commented on GitHub (Aug 19, 2025): Hi @dacagi @abjoseph @mrg358 please update to v0.17.2, thanks for reporting the issue
Author
Owner

@mrg358 commented on GitHub (Aug 19, 2025):

I can confirm my issue is solved in v0.17.1.
Thanks @yusing for quick response. 👍

@mrg358 commented on GitHub (Aug 19, 2025): I can confirm my issue is solved in v0.17.1. Thanks @yusing for quick response. 👍
Author
Owner

@dacagi commented on GitHub (Aug 20, 2025):

Solved! I can also confirm my issues are gone. I had to force refresh with Ctrl+F5 in case someone stumbles upon this. Thanks @yusing as usual.

@dacagi commented on GitHub (Aug 20, 2025): Solved! I can also confirm my issues are gone. I had to force refresh with Ctrl+F5 in case someone stumbles upon this. Thanks @yusing as usual.
Author
Owner

@yusing commented on GitHub (Aug 20, 2025):

Thank you all again. Gonna close this issue now.

@yusing commented on GitHub (Aug 20, 2025): Thank you all again. Gonna close this issue now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#99