Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Temporary failure resolving 'http.kali.org'

  1. #11
    Junior Member
    Join Date
    Apr 2017
    Posts
    2
    One thing to check pointed out by mrkumar on this thread:
    https://forums.kali.org/showthread.p...ling-InRelease

    You don't need to use putty or ssh, regular vi or nano will do from a terminal session but the groupid's were wrong on my ootb nethunter install if anyone else is experiencing the same issue:

    Using putty connect to Nethunter and Run
    vi /etc/passwd,
    Change the line
    _apt:x:104:3004::/nonexistent:/bin/false to _apt:x:0:65534::/nonexistent:/bin/false
    Save and Run apt-get update ,It Works Check it ,
    Explanation: Changing GID 3004 to 65534 ,What is GID 3004 on your system?
    The fact that the _apt user is part of "nogroup" is actually the problem.

  2. #12
    Junior Member
    Join Date
    Sep 2017
    Posts
    1
    Quote Originally Posted by tanyaka View Post
    Yes strange I see this now:

    root@kali:~# apt-get update
    Ign:1 http://http.kali.org/kali kali-rolling InRelease
    Err:2 http://http.kali.org/kali kali-rolling Release
    Could not create a socket for 192.99.200.113 (f=2 t=1 p=6) - socket (13: Permission denied)
    Reading package lists... Done
    E: The repository 'http://http.kali.org/kali kali-rolling Release' does no longer have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.

    Did you not get the permission denied error?

    Quote Originally Posted by Outis View Post
    Just a note to anyone that stumbles across this thread. I was able to fix this by removing chroot and re-adding. This defaulted to kali-rolling instead of the previous repo's and it now works flawlessly without requiring any tweaking.

    **NOTE you must back up any data you have stored in the chroot as you will lose it**
    How exactly would I fix this error?

  3. #13
    Junior Member
    Join Date
    Aug 2017
    Posts
    4
    I just got the error as well. I think Kali has to updated the repositories and it should be fixed hopefully soon. My laptop running Kali is updating fine but my RPi2B is receiving the error.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •