deergon

joined 2 years ago
[–] deergon@lemmy.world 2 points 2 months ago

Great list, thank you!

[–] deergon@lemmy.world 1 points 3 months ago

That looks fantastic :)

[–] deergon@lemmy.world 3 points 4 months ago
[–] deergon@lemmy.world 9 points 5 months ago

That's my approach - once in a while I take a peek at /all, get stressed out and quickly retreat to my curated home again.

[–] deergon@lemmy.world 3 points 7 months ago

That made me laugh, thank you for reminding me of that episode!

[–] deergon@lemmy.world 2 points 8 months ago

Yes. I'm excited to try it out :)

 

Even though it's only research and nowhere near silicon in terms of effectiveness, I find the prospect of maybe one day being able to print simple circuits very exciting :)

[–] deergon@lemmy.world 3 points 1 year ago

Arrival (rewatch)

[–] deergon@lemmy.world 1 points 1 year ago

Have you tried accessing your service url from inside the Traefik container? Eg. wget https://10.13.16.1? Also you seem to be accessing the service url with https, which usually requires insecureSkipVerify=true. Otherwise you might get http-500 error downstream.

[–] deergon@lemmy.world 1 points 1 year ago (2 children)

How about the Traefik access logs (separate from the main log), do they reveal anything?

[–] deergon@lemmy.world 1 points 1 year ago (4 children)

Just a few thoughts:

  • Did you enable access logs in Traefik as well as setting global log level to debug? This usually gives a lot more info about whats going on
  • Are the containers using the same docker network or host network, so they can reach each other?
[–] deergon@lemmy.world 1 points 1 year ago
view more: next ›