ZimaOS 1.7 beta changed how an app tile's Web URL could be edited: users could change the protocol, port and path, but the hostname was tied to the ZimaOS dashboard address. This did not prevent Nginx Proxy Manager or local DNS from serving a custom domain independently.
An IceWhale team reply confirmed at the time that hostname editing was unavailable in the visual editor and said the team planned to bring it back. Current ZimaOS 1.7.1 improves Docker Web URL port settings and URL handling, but its published changelog does not explicitly say that arbitrary hostname editing in the visual form was restored.
What the 1.7 Beta Actually Changed
The user had a local DNS and reverse-proxy setup such as https://app.example.net/. In the beta editor, the app tile itself could no longer be configured to open that custom hostname.
A community reproduction showed that manually setting x-casaos.hostname could remain in YAML while the form and app tile still used the dashboard IP. IceWhale staff then confirmed the visual hostname field was temporarily unavailable.
Your Reverse Proxy Can Still Use the Custom Domain
The limitation described in the thread was about the URL opened by the ZimaOS app tile, not whether Nginx Proxy Manager, AdGuard Home or another DNS/reverse-proxy stack could route a custom hostname to the published app port.
If your proxy already forwards a domain to the correct ZimaOS IP and app port, keep that proxy path separate from the dashboard tile setting. The ZimaOS HTTPS reverse proxy guide covers that architecture.
What ZimaOS 1.7.1 Confirms
The official ZimaOS 1.7.1 changelog lists more flexible Web URL port configuration and improved Docker URL handling. It does not specifically document restoration of the old hostname editor.
The current ZimaOS app metadata reference documents port_map, scheme and index for app entry URLs. Test the current stable editor before rebuilding an established proxy configuration around an older beta behavior.
Do You Need to Downgrade From the Beta?
For this specific issue, the forum advice was not to rush into a rollback because the custom domains themselves still worked through the reverse proxy. Today, the better first step is to move to the current stable ZimaOS release, back up app configuration, and verify the app-tile behavior there.
If you import or repair app YAML, the custom Docker Compose guide is a safer reference than copying a beta-era workaround unchanged.
