Portainer not reachable over network

  • Hello,


    I finally got docker and portainer installed through the webinterface.

    How ever it seems impossible to reach the portainer webinterface through a remote computer.


    Output of

    docker logs -f portainer

    Code
    2021/05/26 21:09:54 server: Reverse tunnelling enabled
    2021/05/26 21:09:54 server: Fingerprint 77:8c:59:a8:2e:b2:b0:33:de:b3:e3:73:a4:90:c6:a0
    2021/05/26 21:09:54 server: Listening on 0.0.0.0:8000...
    2021/05/26 21:09:54 Starting Portainer 2.5.0 on :9000
    2021/05/26 21:09:54 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
    2021/05/26 21:09:54 [DEBUG] [internal,init] [message: start initialization monitor ]
    2021/05/26 21:14:54 [FATAL] [internal,init] No administrator account was created in 5.000000 mins. Shutting down the Portainer instance for security reasons

    Anyone got an idea how to fix this?

    I already changed iptables to legacy and reconfigured my network through omv-firstaid.


    Regards


  • I tried on the shell through SSH by using lynx and 127.0.0.1:9000, which worked, and via the ip 192.168.1.105 on my computer, which didn't work.

    I also kept the 5 minute timeframe in mind.


  • Sorry I forgot the add the port in my post.

    Ofc I tried portainer's webgui by ip+port.


    Maybe iptables is messed up or something. I never messed with it so it should be default.


    docker ps

    Code
    root@Elfish-NAS:~# docker ps
    CONTAINER ID   IMAGE                    COMMAND        CREATED        STATUS         PORTS                                                                                  NAMES
    afbbbac23715   portainer/portainer-ce   "/portainer"   15 hours ago   Up 2 minutes   0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp   portainer

    iptables -S

  • I already changed iptables to legacy and reconfigured my network through omv-firstaid.

    Why you changed iptables?


    If you followed what is on the OMV docker page, just revert it. From my experience, you don't need to change it.

    At least, never touched it and everything works OOTB.


  • Well the comment must be there for a reason.

    My system exactly matches that comment.

    Changing back to nft doesn't work either


    Code
    root@Elfish-NAS:~# lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description:    Debian GNU/Linux 10 (buster)
    Release:        10
    Codename:       buster
    Code
    root@Elfish-NAS:~# dpkg -l | grep openmediavault
    ii  openmediavault                        5.6.7-1                             all          openmediavault - The open network attached storage solution
    ii  openmediavault-anacron                5.0.3                               all          anacron plugin for OpenMediaVault.
    ii  openmediavault-backup                 5.2.4                               all          backup plugin for OpenMediaVault.
    ii  openmediavault-keyring                1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
    ii  openmediavault-omvextrasorg           5.6.1                               all          OMV-Extras.org Package Repositories for OpenMediaVault
    rc  openmediavault-pyload                 1.0.4                               all          OpenMediaVault pyLoad plugin
    rc  openmediavault-sensors                1.0.23                              all          Provides a cpu temperature monitor
  • macom

    Hat das Label OMV 5.x hinzugefügt.
  • macom

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!