apt https

  • This topic has 4 replies, 4 voices, and was last updated Jun 14-7:48 am by stevesr0.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #154580
    Anonymous

      how to do apt via https?
      https in the sources.list.d but it doesn’t work at all.
      packages apt-transport-https and ca-certificates install.
      https doesn’t work.

      #154582
      MrPythoner
      Member

        how to do apt via https?
        https in the sources.list.d but it doesn’t work at all.
        packages apt-transport-https and ca-certificates install.
        https doesn’t work.

        I understand you’re trying to use HTTPS for APT repositories on AntiX 23.1 , but you’re encountering issues. Let’s troubleshoot this step-by-step:

        1. First, ensure you have the necessary packages installed:

        
        sudo apt update
        sudo apt install apt-transport-https ca-certificates curl gnupg
        

        2. Check your sources list. Edit the file:

        
        sudo nano /etc/apt/sources.list
        

        Make sure the URLs use “https://” instead of “http://”.

        3. Check the contents of /etc/apt/sources.list.d/ directory:

        
        ls /etc/apt/sources.list.d/
        

        Ensure any files there also use “https://” URLs.

        4. Update the package lists:

        
        sudo apt update
        

        If you get any errors, please share them.

        5. Check if APT is configured to use HTTPS:

        
        apt-config dump | grep Acquire::https::
        

        This should return some configuration details if HTTPS is properly set up.

        6. Verify that the ca-certificates package is correctly installed and up to date:

        
        sudo update-ca-certificates
        

        7. If you’re behind a proxy, make sure it’s correctly configured for APT:

        
        nano /etc/apt/apt.conf.d/proxy.conf
        

        Add the following line if you’re using a proxy:

        
        Acquire::https::Proxy "https://your.proxy.address:port/";
        

        8. Check if your system time is correct, as SSL certificate validation can fail if the time is significantly off:

        
        date
        

        If these steps don’t resolve the issue, could you please provide:

        1. The exact error message you’re seeing when trying to use HTTPS
        2. The content of one of your HTTPS repository entries (from sources.list or a file in sources.list.d)
        3. The output of apt-config dump | grep Acquire::https::

        With this information, we can better diagnose the problem and find a solution.

        #154753
        Anonymous

          I did what you suggested, but it only helped partially.
          was missing curl
          then i did:
          curl MYREPOSITORY && echo Works
          default repository after installation said it wasn’t working https
          thank you very much

          #179311
          Robin
          Member

            @sarausa? What kind of joke is that answer? And please, remove the hidden spam link from your footer line, otherwise mods will take action for you.

            Windows is like a submarine. Open a window and serious problems will start.

            #179325
            stevesr0
            Member

              Hi all,

              Just noticed this older thread. I wondered why the repo sites were http not https. I will try the directions and see if this works. Not sure if all the http repo sites are also available as https sites.

              I do wonder with the recent promotion of short term certificates if some https sites will be hard to maintain as such without having to override “invalid certificate” popups, unless this doesn’t happen when using the command line.

              The spammy post is already gone, so it was truly serendiptitious for me!

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.