May 18, 20242 yr So this is a minor issue, but is quite annoying. On some docker containers my WebUI links work just fine, on other docker containers the WebUI Placeholders for IP and Port don't get replaced. I haven't found any reason/difference between the containers that are affected and which ones aren't. e.g. my SFTPGo container WebUI link is http://[IP]:[PORT:8080]. This gets rendered directly as <a href="http://[IP]:[PORT:8080]" /> as the link. (so obviously nothing happens when you click on it). I've tried: * Forcing update * Removing container and re-installing from previous apps in CA I can manually set the WebUI link, but as I said, this is really annoying to do.
May 18, 20242 yr Community Expert 2 hours ago, OngoingDetonator said: I haven't found any reason/difference between the containers that are affected and which ones aren't. Could the ones that aren't be created using the compose plugin? If so you have to set the webui link separately on those at the stack configuration.
May 18, 20242 yr Author 8 hours ago, Kilrah said: Could the ones that aren't be created using the compose plugin? If so you have to set the webui link separately on those at the stack configuration. They're all created via Community Applications.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.