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.
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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.
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.
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.
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.
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.
$5 per year? Que? My vps provider gave me a pretty smoking deal, but it’s still a few dollars a month.
Where is this like 40 cent a month provider?
https://www.racknerd.com/NewYear/
They’ve gone up a little, but they’re starting at $11 per year.