• 13 Posts
  • 97 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle








  • I did what you suggested and reduced (1) the number of running services to a minimum and (2) the networks traefik is a member of to a minmum. It didn’t change a thing. Then I opened a private browser window and saw much faster loading times. Great. I then set everything back and refreshed the private browser window: still fast. Okay. Guess it’s not Traefik after all. The final nail in the coffin for my theory: I uses two traefik instances. Homepage still loads its widgets left to right, top to bottom (the order from the yaml file). The order doesn’t correspond to the instances, it’s more or less random. So I’m assuming the slowdown has something to do with (a) either caching from traefik or (b) the way Homepage handels the API request: http://IP:PORT (fast) or https://subdomain.domain.de. Anyway, thanks for your help!


  • Thank you so much for your thorough answer, this is very much a topic that needs some reading/watching for me. I’ve checked and I already use all of those headers. So in the end, from a security standpoint, not even having port 80 open would be best. Then, no one could connect unencrypted. I’ll just have to drill into my family to just use HTTPS if they have any problems.

    It was interesting to see, how the hole process between browser and server works, thanks for clearing that up for me!










  • Pete90@feddit.detoich_iel@feddit.deich🤓iel
    link
    fedilink
    Deutsch
    arrow-up
    19
    ·
    6 months ago

    Methoden, Ergebnisse, Einleitung und Diskussion. Die beiden letzten sind ggf. austauschbar. Quellen sofort eintragen und auf Fehler überprüfen. Ist einfacher, als das nachher 200 mal zu machen. Am besten Zotero nutzen.





  • I tried this. Put a DNS override for Google.com for one but not the other Adguard instance. Then did a DNS lookup and the answer (ip) changed randomly form the correct one to the one I used for the override. I’m assuming the same goes for the scenario with the l public DNS as well. In any case, the response delay should be similar, since the local pi hole instance has to contact the upstream DNS server anyway.