Weird behaviour with ipv6 entries in /etc/hosts

  • Hi, I'm trying to solve an issue recently started to happen with Jellyseerr (using docker compose) but the underlying issue comes from OMV hosts.

    Currently I have ipv6 disabled on all network interfaces, but there is still entries in /etc/hosts for ipv6:

    When trying to login to the jellyseerr with jellyfin account, it tries connecting to jellyfin but it returns some logs refusing to access with ipv6 host (this when I'm using my server local http://servidor.local:8096, if I use directly the ipv4 ip it works):

    Code
    jellyseerr  | 2024-05-10T10:35:00.031Z [error][Jellyfin API]: Something went wrong while getting library content from the Jellyfin server: connect ECONNREFUSED ::1:8096 
    jellyseerr  | 2024-05-10T10:35:00.031Z [error][Jellyfin Sync]: Sync interrupted {"errorMessage":"Invalid auth token"}
    jellyseerr  | 2024-05-10T10:36:00.029Z [debug][Jobs]: Starting scheduled job: Download Sync 
    jellyseerr  | 2024-05-10T10:37:00.030Z [debug][Jobs]: Starting scheduled job: Download Sync 
    jellyseerr  | 2024-05-10T10:37:07.628Z [warn][Auth]: Failed login attempt from user with incorrect Jellyfin credentials {"account":{"ip":"::ffff:172.20.0.1","email":"joaoseixas","password":"__REDACTED__"}}


    If I comment out all ipv6 entries in /etc/hosts it starts working correctly tho. How should I do it then? Will this break anywhere or what's the correct solution here?



    Just an extra comment that this worked before, but due to updates in packages (like node no longer prefering ipv4 entries) this underlying issue popped up. A little context here as well: https://github.com/Fallenbagel/jellyseerr/issues/722

  • chente

    Hat das Thema freigeschaltet.
    • Neu
    • Offizieller Beitrag

    The hostname and FQDN has to be added for ::1 to fix a problem with the name resolution in SaltStack. This entry is absolutely necessary, otherwise deploying Salt states that update grains take several minutes instead of seconds.


    See these commits:

    - https://github.com/openmediava…2b20276f113f86a558a9aad28

    - https://github.com/openmediava…815ce98bd32453a536e184b33


    If i find the corresponding SaltStack issues, i will add them as well.


    This applies to OMV6 and OMV7.

  • votdev

    Hat das Label gelöst hinzugefügt.
  • votdev

    Hat das Label OMV 6.x hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!