Echolot

Members
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Echolot's Achievements

Noob

Noob (1/14)

3

Reputation

  1. @Indigo_5 It can but Traefik would have to point all hosts you want to run through CN to CN. So for example: sonarr.local ↴ ↱ Sonarr Container handbrake.local --> Traefik --> CN --> Handbrake Container
  2. v1.7.0 was released which adds support for proxying to containers using unverified HTTPS. This is useful for services which only listen for SSL connections.
  3. @Alfy1080 I finally got around to adding HTTPS support. Feel free to test the newest version using the ghcr.io/itsecholot/containernursery:dev image.
  4. v1.6.0 was released which adds support for multiple domains that point to the same proxy host / container.
  5. @Alfy1080 I'm an idiot and forgot to run the build command before building the new docker image 😑 The newest release should now properly contain the error handling methods we discussed and should fix your issue (hopefully for real this time 😉). At the moment ContainerNursery only supports HTTP. If this is however a feature that you and maybe some others have a great need for, I would consider implementing it.
  6. @Alfy1080 v1.5.2 was just released which should fix your issue.
  7. @Alfy1080 Thanks for the log entry and bug report. It looks to me like Docker generates an event with some malformed JSON which leads to ContainerNursery crashing. I will wrap the code in some error handling to prevent crashes of ContainerNursery in such an event and release a bug fix release in the next few days.
  8. See the exact same behavior on my 6.9.2 system... Would love to hear an explanation for what is exactly causing this.
  9. v1.5.0 was just released and adds the feature of stoping (and starting) multiple containers for each proxy host. This is especially useful if your application has multiple supporting containers (database, own reverse proxy, etc.).
  10. That is both good and disappointing to hear lol. Means we found a fix but also means that these editors first save an empty file and then save the correct edited file. The file changed event only gets emitted on the first save since there's an internal debounce logic in the library I use. I will push a small bug fix release in the next few minutes with this change.
  11. A small Update v1.4.0 was released, check the second post for the changelog. @guillelopez & @kjames2001 Could you try the config reload issue again with the dev-config tag? ghcr.io/itsecholot/containernursery:dev-config I added a small delay (500ms) after receiving a file change event before trying to read the config file. Maybe this fixes your issue? I sadly still couldn't reproduce this so it's impossible for me to test this on my own.
  12. I just tried this using VSCode as the editor on Mac with the container running, can't reproduce this. Do you maybe use a different encoding than UTF-8? Does the same config file that produces this error work after a restart of the container?
  13. I sadly can't recreate your issue, config reloading works just fine on my machines... Is there anymore detail you can provide?
  14. @guillelopez The fix to the bug you discovered, as well as the configurable listening port update was just released two hours ago. I also added the guide I mentioned to the first post. Let me know if somethings missing.
  15. @guillelopez This is actually a bug! Thanks for reporting this, will look into getting this fixed in the next few days. The port shouldn't be taken into consideration when examining the domain.