Databases
StackOverflow2013
Postsdbo
POapt tools can't resolve host name
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POapt tools can't resolve host name
    primarykey
    data
    text
    <p>I am trying to run <code>apt-get update</code> from a local virtualbox running Debian to pull packages in from a local apt-repository set up on another server on the local network (over a VPN). </p> <p>All other tools are perfectly able to resolve the host name of the local server hosting the apt repository. However, when I run <code>sudo apt-get update</code> I keep getting the following error message:</p> <pre><code>Ign https://[someserver.com/] dev Release.gpg Ign https://[someserver.com/] dev Release Err https://[someserver.com/] dev/main amd64 Packages Err https://[someserver.com/] dev/main amd64 Packages Ign https://[someserver.com/] dev/main Translation-en_GB Ign https://[someserver.com/] dev/main Translation-en Err https://[someserver.com/] dev/main amd64 Packages Couldn't resolve host '[someserver.com' W: Failed to fetch https://[someserver.com/dists/dev/main/binary-amd64/Packages]/ Couldn't resolve host '[someserver.com' E: Some index files failed to download. They have been ignored, or old ones used instead. </code></pre> <p>When I ping 'someserver.com', it comes back fine. If I try to retrieve the Packages list via wget on the command line, the retrieval is successful; it seems to be only apt that can't resolve the host name. </p> <p>Actually I changed someserver.com to google.com for a test, and it returned saying <code>Couldn't resolve '[google.com'</code></p> <p>btw. Are the square-brackets before the hostname as they appear in the error message significant at all? I noticed that when i reverted back to using the official public debian repos, there are no square brackets around the hostnames at all in the log messages and that the update completes successfully. </p> <p>The entry in my sources.list file for the repo is as follows:</p> <pre><code>deb https://username:hex-encoded-password@someserver.com/ dev main </code></pre> <p>Any help would be appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKash.
    1. USKash.
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POapt tools can't resolve host name
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODoes it resolve the hostname correctly if you remove the username and password from the sources.list linbe?
      singulars
      1. POapt tools can't resolve host name
      1. USmkfs
    2. COYep it does. But then it returns a 401 error as follows:
      singulars
      1. POapt tools can't resolve host name
      1. USKash.
    3. COSo the username:password specification is conflicting with the hostname, then. The syntax is legal according to the Debian docs (http://www.debian-administration.org/article/Restrict_Access_To_Your_Private_Debian_Repository), so maybe the password has a bad character (e.g. password has an '@', and apt is decoding it before parsing). I skipped HTTP authentication when I had to password-protect an APT repo many years back. The SSH method is much more reliable.
      singulars
      1. POapt tools can't resolve host name
      1. USmkfs
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload