Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003

    Support
    troubleshooting
    2
    2
    20
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      Nozy last edited by girish

      Hi All

      1st time I have to jump on be runing good for over 2 year

      OK so what I have after a reboot cloudron stop running all show up as no running

      local website 1/2 but no service is running

      0df74504-25ca-460d-9872-6ab9ccab56a5-image.png

      server is up but after running
      6f216d35-4590-4c5b-8391-aa7fe5892620-image.png

      I get this error over and over I think docker not starting right ?

      in the logs
      2023-01-25T03:39:18.524Z box:server ==========================================
      2023-01-25T03:39:18.526Z box:server Cloudron 7.3.4
      2023-01-25T03:39:18.526Z box:server ==========================================
      2023-01-25T03:39:18.686Z box:settings initCache: pre-load settings
      2023-01-25T03:39:18.731Z box:tasks stopAllTasks: stopping all tasks
      2023-01-25T03:39:18.732Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
      2023-01-25T03:39:18.801Z box:shell stopTask (stdout): All tasks stopped

      2023-01-25T03:39:18.807Z box:reverseproxy writeDashboardConfig: writing admin config for mozysswamp.com
      Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
      2023-01-25T03:39:18.896Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
      2023-01-25T03:39:19.024Z box:cloudron onActivated: running post activation tasks
      2023-01-25T03:39:19.025Z box:platform initializing platform
      2023-01-25T03:39:19.026Z box:platform platform is uptodate at version 49.4.0
      2023-01-25T03:39:19.027Z box:platform onPlatformReady: platform is ready. infra changed: false
      2023-01-25T03:39:19.027Z box:apps schedulePendingTasks: scheduling app tasks
      2023-01-25T03:39:19.055Z box:cron startJobs: starting cron jobs with hour 2 and minute 2
      2023-01-25T03:39:19.110Z box:cron backupConfigChanged: schedule 00 00 1,2,3 * * * (Australia/Melbourne)
      2023-01-25T03:39:19.129Z box:cron autoupdatePatternChanged: pattern - 00 00 1,2,3,4,5,23 * * * (Australia/Melbourne)
      2023-01-25T03:39:19.134Z box:cron Dynamic DNS setting changed to false
      2023-01-25T03:39:19.137Z box:dockerproxy startDockerProxy: started proxy on port 3003
      Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003
      at Server.setupListenHandle [as _listen2] (node:net:1446:21)
      at listenInCluster (node:net:1511:12)
      at doListen (node:net:1660:7)
      at processTicksAndRejections (node:internal/process/task_queues:84:21)

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @Nozy last edited by

        @Nozy said in Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003:

        2023-01-25T03:39:19.137Z box:dockerproxy startDockerProxy: started proxy on port 3003
        Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003

        Something else is running port 3003. Can you try lsof -i :3003 . That should give you the pid of the process that is using that port. Did you happen to install anything outside of Cloudron on the server?

        You can also check systemctl status docker to see if docker is running and also docker ps to check if the containers are running.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Powered by NodeBB