Want to subscribe to topics you're interested in?
Become a Member

centmin.sh Error: unable to connect to Github.com repo right now try again later (persistent issue)

Discussion in 'Bug Reports' started by ENF, Jul 11, 2023.

  1. ENF

    ENF SquareEnix (Eng.) Premium Member

    18
    4
    3
    May 9, 2016
    Tokyo, Japan
    Ratings:
    +11
    Local Time:
    12:16 AM
    1.23.4
    10.X
    One client server (of many) cannot update Centminmod as noted below:

    Centminmod Menu

    Code:
     [Centminmod Menu 23 > 2]
    Detected Centmin Mod Github Remote Repo Changes
    setting up fresh /usr/local/src/centminmod code base to match
    
    time git clone -b 124.00stable --depth=1  centminmod
    fatal: repository 'centminmod' does not exist
    
    real    0m0.001s
    user    0m0.000s
    sys     0m0.001s
    
    Error: wasn't able to successfully update /usr/local/src/centminmod code base
           restoring previous copy of /usr/local/src/centminmod code base
    
    CMUPDATE
    Code:
    [ch199415@pantok02s152]# cmupdate
    
    Error: unable to connect to Github.com repo right now
    try again later
    
    if issue persists, report it on official Centmin Mod community
    https://community.centminmod.com/forums/install-upgrades-or-pre-install-questions.8/
    This has been an ongoing issue over the past few days that I've been looking at it. Other servers in the same DC location that have Centminmod running, have no issues to run the update. I have read other threads that outlined steps to help resolve the issue and I will note the following outputs (from the problem server):


    CURL Output for Github Centminmod Repo
    Code:
    [ch199415@pantok02s152]# curl -I https://github.com/centminmod/centminmod
    HTTP/1.1 200 OK
    Server: GitHub.com
    Date: Tue, 11 Jul 2023 03:13:30 GMT
    Content-Type: text/html; charset=utf-8
    Vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
    ETag: W/"c7228c1ef99061a3b140a8f718882add"
    Cache-Control: max-age=0, private, must-revalidate
    Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
    X-Frame-Options: deny
    X-Content-Type-Options: nosniff
    X-XSS-Protection: 0
    Referrer-Policy: no-referrer-when-downgrade
    Content-Security-Policy: default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com productionresultssa0.blob.core.windows.net/ productionresultssa1.blob.core.windows.net/ productionresultssa2.blob.core.windows.net/ productionresultssa3.blob.core.windows.net/ productionresultssa4.blob.core.windows.net/ wss://*.actions.githubusercontent.com github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src 'self' data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ user-images.githubusercontent.com/ private-user-images.githubusercontent.com opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ private-user-images.githubusercontent.com; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
    Set-Cookie: _gh_sess=VFmkLBaGfK7VboEgTgNWZqkjQ%2FNP29%2BAZSqTVzF7aGkeeV%2BWl3jDNToqkEJxMdSewjpLxKtyJ%2BHQy0pzZjp7sr4T82dH3g8bspgog5H%2FCi3AoCAdCAzq%2FKm9Mept7Vbj0OlZzFoXMZvvTT%2BuyLdGafG2Ss15Kh3CJGJ3wTGNwHrkUfQSGV0c2nHYzSbGrCTeC74Kc5rRoKUrpd94Z3CLCRktskPV3jUDRQKhVs5oKM0YVZc%2Bt4eyiU%2Fxo%2FuzJ%2FduIvC9mUcmD%2FxnFMmI9WgS%2Bw%3D%3D--QkyL5dN9MWFRsver--NU5XC1m0l1yabaF21ED47w%3D%3D; Path=/; HttpOnly; Secure; SameSite=Lax
    Set-Cookie: _octo=GH1.1.6317876.1689048809; Path=/; Domain=github.com; Expires=Thu, 11 Jul 2024 03:13:29 GMT; Secure; SameSite=Lax
    Set-Cookie: logged_in=no; Path=/; Domain=github.com; Expires=Thu, 11 Jul 2024 03:13:29 GMT; HttpOnly; Secure; SameSite=Lax
    Accept-Ranges: bytes
    X-GitHub-Request-Id: 8A34:0C29:300C24:338AAE:64ACD6E9
    I'm perplexed as to why this machine cannot get updates whereas others on the same segment, can. I hesitate posting this as a bug/question, but other than blowing this machine up and rebuilding it, I don't see what other option I have unless I'm overlooking something stupidly obvious that would block this update. Obviously the server can connect to Github, but the cmupdate disagrees.
    • CentOS Version: CentOS 7
    • Centmin Mod Version Installed: 124.00stable
    • Nginx Version Installed: 1.23.4
    • PHP Version Installed: 8.0.29
    • MariaDB MySQL Version Installed: MariaDB 10.3.9
    • When was last time updated Centmin Mod code base ? : Approximately 21 Days ago.
    • Persistent Config: N/A
     
  2. eva2000

    eva2000 Administrator Staff Member

    51,743
    11,946
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,438
    Local Time:
    1:16 AM
    Nginx 1.25.x
    MariaDB 10.x
    How far back is this Github issue going as seeing from Github status history there were git pull issues for July 3, 5, and 7 https://www.githubstatus.com/history

    What doe that server's local DNS resolvers look like in /etc/resolv.conf ?

    You can always try a clean Centmin Mod menu code refresh with these commands for replacement by wiping /usr/local/src/centminmod as outlined similar to update guide here for older than .07 releases.

    replace branchname with branch you want either 124.00stable or 130.00beta01

    first verify that github repo link is working and you don't have connectivity issues to github.com via curl header inspection - look for HTTP 200 status code = ok
    Code (Text):
    curl -I https://github.com/centminmod/centminmod
    

    example
    Code (Text):
    curl -I https://github.com/centminmod/centminmod
    HTTP/1.1 200 OK
    Server: GitHub.com
    Date: Fri, 03 May 2019 09:37:50 GMT
    Content-Type: text/html; charset=utf-8
    Status: 200 OK
    

    Then do clean Centmin Mod code replacement using below SSH commands
    Code (Text):
    branchname=124.00stable
    cd /usr/local/src
    rm -rf centminmod*
    git clone -b ${branchname} --depth=1 https://github.com/centminmod/centminmod.git centminmod
    cd centminmod
    ./centmin.sh
     
  3. ENF

    ENF SquareEnix (Eng.) Premium Member

    18
    4
    3
    May 9, 2016
    Tokyo, Japan
    Ratings:
    +11
    Local Time:
    12:16 AM
    1.23.4
    10.X
    These issues have been going at least since July 8th and still an issue as of July 11th (today).
    Nameservers in resolv.conf: (don't believe this was ever touched during original install)
    Code:
    nameserver 139.162.71.5
    nameserver 139.162.75.5
    nameserver 139.162.70.5
    
    The above clean install works but after the clean install, the cmupdate and/or the centmin menu update still have the connection issues to the Github repo.

    Code:
    Cloning into 'centminmod'...
    remote: Enumerating objects: 701, done.
    remote: Counting objects: 100% (701/701), done.
    remote: Compressing objects: 100% (513/513), done.
    remote: Total 701 (delta 236), reused 417 (delta 165), pack-reused 0
    Receiving objects: 100% (701/701), 23.57 MiB | 4.61 MiB/s, done.
    Resolving deltas: 100% (236/236), done.
    Code:
    cmupdate
    
    Error: unable to connect to Github.com repo right now
    try again later
    
    if issue persists, report it on official Centmin Mod community
    https://community.centminmod.com/forums/install-upgrades-or-pre-install-questions.8/
    
     
  4. eva2000

    eva2000 Administrator Staff Member

    51,743
    11,946
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,438
    Local Time:
    1:16 AM
    Nginx 1.25.x
    MariaDB 10.x
    what if you can nameservers from
    Code (Text):
    nameserver 139.162.71.5
    nameserver 139.162.75.5
    nameserver 139.162.70.5
    

    to
    Code (Text):
    nameserver 8.8.8.8
    nameserver 8.8.4.4
    
     
  5. ENF

    ENF SquareEnix (Eng.) Premium Member

    18
    4
    3
    May 9, 2016
    Tokyo, Japan
    Ratings:
    +11
    Local Time:
    12:16 AM
    1.23.4
    10.X
    We located the issue.
    Something in the /etc/csf.deny file was blocking this particular connection.
    As a test, we dumped the csf.deny file and reloaded csf.
    After the csf -f and csf -r commands, centminmod updates functioned normally.

    Sorry for the trouble in this case.
     
  6. eva2000

    eva2000 Administrator Staff Member

    51,743
    11,946
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,438
    Local Time:
    1:16 AM
    Nginx 1.25.x
    MariaDB 10.x
    Ah CSF Firewall!
     
  7. ENF

    ENF SquareEnix (Eng.) Premium Member

    18
    4
    3
    May 9, 2016
    Tokyo, Japan
    Ratings:
    +11
    Local Time:
    12:16 AM
    1.23.4
    10.X
    A further investigation into the change logs revealed that another administrator setup some new IP range blocks due to some trouble from those networks. (It was an approved changed, but I think not properly vetted...) We reverted the change to a previous version and all is well. We're now looking at those range blocks to avoid a repeat occurrence.

    Admittedly, first time I've had this happen with a server with Centminmod on it. Stepping back through the whole issue is where I figured out that we had ignored the csf config on that specific box. Kind of a facepalm moment. :eek: