I’m using the Nginx Proxy Manager from Truecharts and since the most recent update (2.11.1_9.13.0) the app isn’t deploying anymore with the following message in the event history:

Startup probe failed: dial tcp 172.16.0.75:81: connect: connection refused

Has anyone figured out how to fix this?

And I can’t use the app from TrueNAS because I can’t set the ports to anything below 9000 because of the LoadBalancer they are using for their apps. I also tried using the docker image directly and deploy it as a custom app in TrueNAS and set a static IP for it but when going to the IP it doesn’t load anything.

Edit: even an older version of the app is not deploying anymore (2.11.1_8.5.0)

Edit2: well, at least the older version deployed now I guess it just took a very long while to do so.

  • WeirdGoesPro@lemmy.dbzer0.comEnglish
    2·
    3 months ago

    Are you using Nginx to make your app available on the web? If you are on a home internet connection, how confident are you that your ISP has given you a static IP?

    Running Nginx and Tailscale to route traffic through a VPS with a static IP has been way more reliable for me than any attempt at static IP hosting from a home connection in the past. At $5-$15 per year, a VPS is cheaper than the hassle of troubleshooting with an ISP at home.

  • czl@lemmy.noice.socialEnglish
    2·
    3 months ago

    I’ve noticed that my app takes a while to deploy, so I just wait for it to finish and eventually the probe works. 10-ish minutes usually works.

  • __init__@programming.devEnglish
    1·
    3 months ago

    All that message means is “the thing didn’t start” and isn’t gonna tell you anything about why. You’d need to dig into pod logs or something to see if you can find the actual error that is preventing startup.

    • skittlebrau@lemmy.worldEnglish
      1·
      3 months ago

      Would there be any technical reason why those logs aren’t displayed in an easy to view location in the UI? I’ve come across too many instances of a TN/Kubernetes app that’s been rubbing perfectly fine for days and it suddenly gets stuck deploying. I feel like with regular docker it’s much easier to troubleshoot.

      • __init__@programming.devEnglish
        1·
        3 months ago

        I’m not actually familiar with truenas or its ui, but if you have kubectl access you should be able to poke around in the logs and see what’s going on. I’m not sure if these logs are shown in the ui anywhere. With helm, there are so many different things it could be that there’s no use in speculating without some logs.