Hello, have a problem with ZimaOS. I joined the open beta program, and it has been great so far, exept installing new apps. I run Adguard Home as my main DNS server, and I also run nginx proxy manager with my own certificates, which are applied to my devices. I use my own local domains, for example ZimaOS dashboard is run at https://zimaos.vostro.net/
Apps are run as https://[App Name].vostro.net/
I usually apply this configuration at the top of the app installer, as it makes accessibility easier. But now I cannot do this?
Is there a way around this, or to downgrade back to stable / stock? I need to be able to customise the URL as all of my services are set up like this. Thank you for reading this.
I reproduced this on my ZimaCube running ZimaOS 1.7.0-beta1.
The app editor now locks the hostname to the address used for the ZimaOS dashboard. Only the protocol, port and path can be changed.
I also tested adding a custom hostname directly under x-casaos in YAML. The value remained after saving, but ZimaOS ignored it. The Form still displayed the dashboard IP, and the app tile continued opening the IP address and published port.
Your AdGuard Home and Nginx Proxy Manager setup should still work independently. You can continue accessing each service directly through addresses such as https://app.vostro.net/, provided Nginx Proxy Manager forwards that hostname to the correct ZimaOS IP and published app port. The problem is specifically that the ZimaOS app tile can no longer be configured to open that custom address.
I believe this is a regression or removed capability in the new 1.7 app editor and the editable hostname field should be restored. I would not downgrade yet because the custom domains should remain functional outside the ZimaOS app tiles. If a rollback becomes necessary, the current RAUC slot status should be checked first rather than assuming the stable release is still available.
Thanks to @gelbuilding for clarifying this problem. At present, the hostname of the application cannot be edited in the visual editor for the time being, but we have retained the original x-casaos.hostname field to open the hostn defined by the application. Ame, but the host display will not display the value at present. Thank you for showing us that the editing hostname function is so popular in the community. My partners and I will launch the editing form function as soon as possible.
