Skip to main content

Clean installed cPanel, sitejet is not working

Comments

13 comments

  • rbairwell

    The SSL certificate on https://api.sitehub.io did renew on the 30th of January at 23:16 - so it's possible your server may have cached the old certificate or just caught it in the middle of renewing.

    If you try it again, are you still having the same issue? If so, try running from your server:

     echo | openssl s_client -connect api.sitehub.io:443 2>/dev/null | openssl x509 -noout -serial -subject -issuer -dates -ext subjectAltName

    to fetch details of the SSL certificate being presented. I am getting one looking like:

    serial=042A3E416F3F1C5981C1EAFEE3F40B03CCDE
    subject=CN = preset.sitehub.io
    issuer=C = US, O = Let's Encrypt, CN = R3
    notBefore=Jan 30 23:16:48 2024 GMT
    notAfter=Apr 29 23:16:47 2024 GMT
    X509v3 Subject Alternative Name:
        DNS:api.sitehub.io, DNS:cms.sitehub.io, DNS:my.sitehub.io, DNS:partner.sitehub.io, DNS:preset.sitehub.io, DNS:preview.sitehub.io

    What do you get? I suspect you might have a result similar to:

    serial=3D845BFD89D32B44
    subject=O = NextDNS Inc., CN = blockpage.nextdns.io
    issuer=O = NextDNS Inc., CN = NextDNS Blockpage Edge CA
    notBefore=Jan 31 00:00:01 2024 GMT
    notAfter=Feb  5 00:00:01 2024 GMT
    X509v3 Subject Alternative Name: 
        DNS:api.sitehub.io

    indicating that, in this case, NextDNS (who provide "ad-free DNS resolution") redirected your server to an alternative host as it deemed api.sitehub.io adware (I doubt NextDNS does, but I just mocked this response for demonstration purposes). 

    0
  • Turner Hill

    the result is as below

     

    echo | openssl s_client -connect api.sitehub.io:443 2>/dev/null | openssl x509 -noout -serial -subject -issuer -dates -ext subjectAltName

    serial=042A3E416F3F1C5981C1EAFEE3F40B03CCDE
    subject=CN = preset.sitehub.io
    issuer=C = US, O = Let's Encrypt, CN = R3
    notBefore=Jan 30 23:16:48 2024 GMT
    notAfter=Apr 29 23:16:47 2024 GMT
    X509v3 Subject Alternative Name: 
        DNS:api.sitehub.io, DNS:cms.sitehub.io, DNS:my.sitehub.io, DNS:partner.sitehub.io, DNS:preset.sitehub.io, DNS:preview.sitehub.io

    0
  • Turner Hill

    Environment : Proxmox LXC container

    OS : Almalinux 8.9 and Ubuntu 20.04 also same as below

    0
  • Turner Hill

    when I connect https://my.sitehub.io/login, it works

     

     wget https://my.sitehub.io/login
    --2024-02-01 12:30:06--  https://my.sitehub.io/login
    Resolving my.sitehub.io (my.sitehub.io)... 88.198.22.168, 136.243.5.208
    Connecting to my.sitehub.io (my.sitehub.io)|88.198.22.168|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [text/html]
    Saving to: ‘login’

    login                                                      [ <=>                                                                                                                        ]  21.22K  --.-KB/s    in 0.1s    

    2024-02-01 12:30:08 (211 KB/s) - ‘login’ saved [21725]

    0
  • cPRex Jurassic Moderator

    Can you force a cPanel update with "/scripts/upcp --force" and then try again? 

    0
  • Turner Hill

    I tried with /scripts/upcp --force and reboot. but same as before.

    Would you install cPanel on Promox LXC ?

     

    0
  • cPRex Jurassic Moderator

    Honestly, no, I wouldn't use that system.  We haven't tested any of the version 8 operating systems on that, so I can't guarantee cPanel will be stable there:

    https://docs.cpanel.net/knowledge-base/general-systems-administration/linux-containers/

    "We have not tested LXC on CloudLinux 8 or higher, AlmaLinux OS, or Rocky Linux™ servers."

    0
  • Turner Hill

    Hello Sir,

    Do you recommend CentOS 7 ?

    0
  • cPRex Jurassic Moderator

    No, at this point you would want to be using AlmaLinux 8. 

    0
  • Turner Hill

    If Sitejet works well on CentOS 7, I can use CentOS 7

     

    SItejet works well on CentOS 7 ?

    0
  • cPRex Jurassic Moderator

    Sitejet isn't dependent on the operating system.

    You really don't want to build a new server with CentOS 7 today, as it will reach end of life in June.

    0
  • Turner Hill

    I am trying to install on CentOS 7 but not supported.

     

    0
  • cPRex Jurassic Moderator

    Exactly

    0

Please sign in to leave a comment.