apt update - W: Failed to fetch http:/..........................

  • Hello, how can i solved thin problem?


    Code
    apt update



    The OMV webgui doesn't help.


    My install script:


    https://github.com/OpenMediaVa…-Developers/installScript


    Greets


    openmedianer


    I will try: Failed to fetch ERRORS


    This doesn't help.

  • Hello, i have the same problem again.



    My /etc/network/interfaces

    How can i solved the problem?

  • What package is responsible for the DNS name resolution and/or maintaining /etc/resolv.conf? Is /etc/resolv.conf a link and if yes to which file?


    My /etc/network/interfaces

    The dns entries are prefixed by dns-. Also they don't stand on their own. They are added to each static network interface configuration. Why do you want to use the Google DNS servers anyway? Your network interface enp0s3 gets all its data using DHCP. Why isn't the DHCP server assigning the correct DNS servers to the client?

  • I don't understand you, what did you mean?


    I use ssh connection to my omv 5 machine.


    My first problem:


    Code
    root@deb10:/home/openmedianer# docker pull portainer/portainer-ce
    Using default tag: latest
    Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:33237->[::1]:53: read: connection refused
    root@deb10:/home/openmedianer#

    and than


    https://nopaste.linux-dev.org/?1329193

  • Networking in OMV5 is configured using netplan with a yaml file

    I tested the OP's configuration. If I have a device using DHCP and if I add an additonal nameserver via the OMV GUI, a file in /etc/netplan/ is created, but the contents are not picked up. /etc/resolv.conf still contains only the DNS server assigned via DHCP.

  • I use ssh connection to my omv 5 machine.


    My first problem:


    Code
    root@deb10:/home/openmedianer# docker pull portainer/portainer-ce
    Using default tag: latest
    Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:33237->[::1]:53: read: connection refused
    root@deb10:/home/openmedianer#

    A quick search did reveal this thread. This comment seems relevant.

  • My network is DHCP this the yaml file related to my nic;

    I have added cloudflare to the DNS of the nic within network interfaces on OMV WebUI. But /etc/resolv.conf picks up and adds the DNS from the DHCP server as a secondary DNS;

    this is how it should look, both for the yaml file and resolv.conf

    Raid is not a backup! Would you go skydiving without a parachute?

  • My new

    /etc/network/interfaces


    now i get




    How can i solved my problem?


    Is this a SWAG problem?


    https://docs.linuxserver.io/general/swag

  • I don't understand you, what did you mean?

    Ok, let me break it down. You report issues with the DNS system. But docker images don't interfere with the host's network settings. So why is the docker image relevant and why do you point to the howto?


    Second: Your networking device gets its settings via DHCP. So why does the system in question not get a valid DNS server from the DHCP server?


    Third: There are different tools to manage /etc/resolv.conf. That's why editing this file is often a bad idea because the contents can get lost. Knowing which service manages this file tells us where to put our settings. E.g. it is usually fine for static configurations to put the dns settings into /etc/network/interfaces. If systemd-resolvd is involved it can be necessary to put the DNS settings into /etc/systemd/resolved.conf. And there are more tools. That's why I ask which service is managing the file (often the service leaves a hint inside /etc/resolv.conf) and/or if the file is a link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!