[6.8.2] Docker Container 'WebUI' IP is wrong

If this is a bug related to unRaid, and not the template itself, you need to also post the applicable xml file from /config/plugins/dockerMan/templates-user with it set up so that it acts the way as described in the OP.

Hi,

I would guess its unraid at fault considering all other containers are fine, but as i'm not familiar with the system at that level and i'm flagging it for diagnosis...so you tell me where the fault lies 

Equally, is there a guide for the docker template pull you mention, i don't recall seeing info on it in the bug reporting sticky.

 

Thanks.

The path he gave is where all your templates are on your Flash drive.

Thanks, I'll grab it when I get home and post it.

XML from NCP container as follows - 

 

Looks like the IP is wrong in there, is it safe to edit that file?

---------------

  <Name>nextcloud</Name>
  <Repository>ownyourbits/nextcloudpi</Repository>
  <Registry>https://hub.docker.com/r/ownyourbits/nextcloudpi</Registry>
  <Network>proxynet</Network>
  <MyIP/>
  <Shell>sh</Shell>
  <Privileged>true</Privileged>
  <Support>https://forums.unraid.net/topic/84549-support-nextcloudpi/</Support>
  <Project>https://ownyourbits.com/</Project>
  <Overview>This is a template for the Nextcloudpi docker container, this is an all in one solution for someone wanting to run Nextcloud on their unRaid server. More inf>
https://ownyourbits.com/&#xD;
https://hub.docker.com/r/ownyourbits/nextcloudpi&#xD;
&#xD;
Before hitting start, select advanced view in the top right corner, add your servers IP address e.g. 192.168.1.5 or the IP of the container if you specify a unique one.<>
  <Category>Cloud: Tools: MediaServer:Music MediaServer:Photos</Category>
  <WebUI>https://192.168.1.252:444/</WebUI>
  <TemplateURL>https://raw.githubusercontent.com/Dimtar/unraidtemplates/master/nextcloudpi/nextcloudpi.xml</TemplateURL>
  <Icon>https://github.com/Dimtar/unraidtemplates/raw/master/nextcloudpi/logo.jpg</Icon>
  <ExtraParams/>
  <PostArgs>Enter server or container IP here e.g. 192.168.1.5</PostArgs>
  <CPUset/>
  <DateInstalled>1580657913</DateInstalled>
  <DonateText/>
  <DonateLink/>
  <Description>This is a template for the Nextcloudpi docker container, this is an all in one solution for someone wanting to run Nextcloud on their unRaid server. More >
https://ownyourbits.com/&#xD;
https://hub.docker.com/r/ownyourbits/nextcloudpi&#xD;
&#xD;
Before hitting start, select advanced view in the top right corner, add your servers IP address e.g. 192.168.1.5 or the IP of the container if you specify a unique one.<>
  <Networking>
    <Mode>proxynet</Mode>
    <Publish>
      <Port>
        <HostPort>81</HostPort>
        <ContainerPort>80</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
      <Port>
        <HostPort>444</HostPort>
        <ContainerPort>443</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
      <Port>
        <HostPort>4443</HostPort>
        <ContainerPort>4443</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
    </Publish>
  </Networking>
  <Data>
    <Volume>
      <HostDir>/mnt/user/Nextcloud/</HostDir>
      <ContainerDir>/data</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
  </Data>
  <Environment/>
  <Labels/>
  <Config Name="Nextcloud data folder" Target="/data" Default="/mnt/user/appdata/nextcloudpi" Mode="rw" Description="The folder to store all data related to the containe>
  <Config Name="HTTP web port" Target="80" Default="80" Mode="tcp" Description="Non secure web port" Type="Port" Display="always" Required="false" Mask="false">81</Confi>
  <Config Name="HTTPS web port" Target="443" Default="443" Mode="tcp" Description="Secure web port" Type="Port" Display="always" Required="false" Mask="false">444</Confi>
  <Config Name="Panel web port" Target="4443" Default="4443" Mode="tcp" Description="Port to serve the Nextcloudpi management panel on." Type="Port" Display="always" Req>
</Container>

My guess is you put that IP in there yourself. It doesn't look like the original template has a fixed IP in it.

 

Your guess is incorrect

I have not edited any XML in the setup of this, or any other, container as I've not had a reason to edit.

 

Is it safe to edit after the fact? I mean it doesnt solve what appears to be a bug, but as a workaround, its fine.

3 minutes ago, boomam said:

Is it safe to edit after the fact? I mean it doesnt solve what appears to be a bug, but as a workaround, its fine.

Yes

 

And, FWIW the entry if you install it today from CA is  https://[IP]:[PORT:443]/

ok, excellent.

& well spotted/advised on that XML. 🙂

 

I edited it to be the correct server IP/port and everything's fine again in the GUI.

A mystery as to why it got the wrong IP to begin with, but at least it was comparatively easy to resolve.

Changed Status to Solved

25 minutes ago, boomam said:

Your guess is incorrect

I have not edited any XML in the setup of this, or any other, container as I've not had a reason to edit.

Users do not normally access the XML file directly.  You could have set that IP address via the option to Edit the container settings in the GUI as that generates the XML file.