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

  • Could be, I upgraded from 3 to 4, but for 5 I decided on a clean install and having tested the ISO and the Debian net install + script in a VM, I finally decided to go with the ISO.

    Would you mind sending me the output of systemctl list-units --full --no-pager? I'd like to compare our running services (in private is fine). Oh and: is your /etc/resolv.conf a symlink by any chance?

  • Ok. Then the difference is probably that your system runs the systemd-resolvd service (sudo systemctl status systemd-resolvd). That service is enabled by default in Buster. And then the additional DNS server shows up in /var/run/systemd/resolve/resolv.conf. But this service is disabled on upgraded systems and must be enabled manually (a restart will start it). Also the symlink must be created manually. So then this must be handled during upgrades as well.

  • Hello my way:


    - Debian 10.7 install in Virtualbox

    - OMV 5 install with https://github.com/OpenMediaVa…-Developers/installScript

    - Install Nextcloud with the GUIDE [How-To] Nextcloud with Letsencrypt using OMV and docker-compose


    I'm tried to install an new portainer container, i get wiht error:


    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#

    Than tried solved the problem wiht "apt update" an i get:


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

  • openmedianer , please follow these instructions. Also you will have to do this:


    sudo systemctl enable systemd-resolved

    sudo systemctl start systemd-resolved

    sudo ln -sf /var/run/systemd/resolve/resolv.conf /etc/resolv.conf (EDIT: according to the contents the symlink already exists)


    This will enable the systemd name resolver service and should hopefully get you in sync with a vanilla OMV5 installation (thanks geaves). After you've done this: check cat /etc/resolv.conf (does it contain a nameserver entry now) and ping google.com and report back.

  • Debian 10.7 install

    Debian net install? because that is what is recommended installing ssh server only then run the script.


    Whatever you have done your installation is wrong!! the only way to resolve it is to reinstall, going any further is a complete waste of time and effort.

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

  • I must restore my system (2021-01-31), cook dinner is more important.

    You get the information later.


    -

    -


    Code
    ping google.com
    ping: google.com: Name or service not known


    I will try with: Failed to fetch ERRORS 


    Quote


    Use the apt-get clean button in OMV Extras... That should fix this.


    It doesn't solved my problem.


    Did you have more input for me or should i make a new install?

  • Did you have more input for me or should i make a new install?

    Now again open the OMV GUI. Go to Settings > Network and choose the Interfaces tab. Choose your interface and scroll down to Advanced settings and in the DNS servers field add 8.8.8.8. Save and apply. You might have to restart the networkd service:


    sudo systemctl restart systemd-networkd (not sure if OMV does it itself)


    Output the results of ls -lA /etc/resolv.conf and cat /etc/resolv.conf.

  • Quote

    Now again open the OMV GUI. Go to Settings

    Why we shouldn't use ssh connection?


    Now OMV 5 GUI:


    https://i.imgur.com/zjkDiQ9.jpg


    dleidert

    You are the best, your solution solved the fetch problem. :-)


    Code
    ls -lA /etc/resolv.conf
    lrwxrwxrwx 1 root root 32 Jan 31 12:22 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf





    Where was my mistake, I followed the GUIDE [How-To] Nextcloud with Letsencrypt using OMV and docker-compose ?

    I the fetch problem a VirutalBox problem?

  • I the fetch problem a VirutalBox problem

    This is not a VirtualBox problem, the problem is you!! not following tried and tested methods of installation dleidert should be give a medal in his dogged persistence in helping you, he's far more technically minded than I am when it comes to Linux.


    But you had gone way 'off piste' with your configuration of the network, and you were obviously getting confused with OMV's configuration and that of Nextcloud

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

Participate now!

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