ISSUE SSL FOR HOSTNAME not working

Hi everyone,

I've performed a fresh install and successfully added my first website and domain. I'm now wanting to access cyberpanel via a domain and not the IP.

I've created a subdomain and updated the host SSL to this sub domain but the new URL just times out. The IP method of access still works, but not via the new sub domain. There were no error when creating anything, so I'm looking to be pointed in the right direct.

I followed these instructions, but no luck.

https://docs.cyberpanel.net/doku.php?id=cyberpanel-on-ssl

Thanks in advance!

Comments

  • If it times out then DNS should not be working yet, because even if CyberPanel fails to obtain Lets Encrypt SSL, self-signed SSL is issued.

    And you should be able to access CyberPanel via your domain.

    To be sure, please paste logs from CyberPanel main log file, which is at:

    /serverstatus/cyberCPMainLogFile
  • Many thanks!

    It was a DNS issue (using cloudflare) which is now resolved.
  • I have problem I can't issue ssl for hostname I get SSL Issued. You can now access CyberPanel at: https://"domain":8090
  • insha said:

    I have problem I can't issue ssl for hostname I get SSL Issued. You can now access CyberPanel at: https://"domain":8090

    What do you see in CyberPanel main log file? Also mention the version.
  • 1.64. I can't output log with that command I get not exist. What should I use for checking log file?
  • Logs can be seen at: /serverstatus/cyberCPMainLogFile
  • It's empty, can send you my root access in private?
  • edited November 2018
    I have same problem.

    When i want to add site with ssl support i see

    "Cannot issue SSL. Error message: 0,283 Failed to obtain SSL for domain. [issueSSLForDomain]"


    It's my cyberCPMainLogFile

    I solve my problem.
  • muratduru said:

    I have same problem.

    When i want to add site with ssl support i see

    "Cannot issue SSL. Error message: 0,283 Failed to obtain SSL for domain. [issueSSLForDomain]"


    It's my cyberCPMainLogFile

    I solve my problem.

    hey, i am also facing the same problem how did you solved yours?
  • Hello, I have a problem with renewing the certificate.
    error:
    Can not issue SSL. Error message: 0.283 Failed to obtain SSL for domain. [IssueSSLForDomain]

    log
    [11-22-13-Sat-Dec-2018] Failed to obtain SSL, issuing self-signed SSL for: wizbox.pl
    [11-24-06-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-24-15-Sat-Dec-2018] Failed to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-24-15-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl
    [11-24-17-Sat-Dec-2018] Failed to obtain SSL, issuing self-signed SSL for: wizbox.pl
    [11-25-01-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-25-03-Sat-Dec-2018] Failed to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-25-03-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl
    [11-25-05-Sat-Dec-2018] Failed to obtain SSL, issuing self-signed SSL for: wizbox.pl
    [11-26-05-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-26-08-Sat-Dec-2018] Failed to obtain SSL for: wizbox.pl and: www.wizbox.pl
    [11-26-08-Sat-Dec-2018] Trying to obtain SSL for: wizbox.pl
    [11-26-10-Sat-Dec-2018] Failed to obtain SSL, issuing self-signed SSL for: wizbox.pl


    certbot - log
    2018-12-02 18:35:05,308:DEBUG:certbot.main:certbot version: 0.21.1
    2018-12-02 18:35:05,308:DEBUG:certbot.main:Arguments: ['-d', 'wizbox.pl']
    2018-12-02 18:35:05,308:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
    2018-12-02 18:35:05,324:DEBUG:certbot.log:Root logging level set at 20
    2018-12-02 18:35:05,324:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
    2018-12-02 18:35:05,325:DEBUG:certbot.log:Exiting abnormally:
    Traceback (most recent call last):
    File "/usr/bin/certbot", line 11, in
    load_entry_point('certbot==0.21.1', 'console_scripts', 'certbot')()
    File "/usr/lib/python2.7/site-packages/certbot/main.py", line 1240, in main
    return config.func(config, plugins)
    File "/usr/lib/python2.7/site-packages/certbot/main.py", line 1142, in renew
    renewal.handle_renewal_request(config)
    File "/usr/lib/python2.7/site-packages/certbot/renewal.py", line 375, in handle_renewal_request
    raise errors.Error("Currently, the renew verb is capable of either "
    Error: Currently, the renew verb is capable of either renewing all installed certificates that are due to be renewed or renewing a single certificate specified by its name. If you would like to renew specific certificates by their domains, use the certonly command instead. The renew verb may provide other options for selecting certificates to renew in the future.

  • of course, I already had the version

    Current Version
    1.7
    Build
    4
    Latest Version
    1.7
    Latest Build
    4

    the problem is still the same, some other ideas?
  • @mateusz2552

    Submit a ticket, let see what is wrong.
  • How do I send a ticket?
  • I'm now having this same issue with just one domain. "283 Failed to obtain SSL for domain. [issueSSLForDomain] [404]"
  • That is very easy to troubleshoot, https://cyberpanel.net/docs/troubleshooting-cyberpanel/

    Mostly it is too many failed attempts, you can also try to remove SSL directory and issue from CyberPanel again

    rm -rf /etc/letsencrypt/live/domain.com
  • OK. I will let it wait about a week and hopefully it takes. I did already try reissuing after deleting the live folder, though.
  • edited February 13
    I am well aware of the rate limits, but I had actually found another potential problem. If the site already has a https redirect in place in the Rewrite Rules/.htaccess file and there is no valid SSL certificate, then it will be inaccessible including for the Let's Encrypt challenge. Here are the details:

    /home/office.techandtiny.com/public_html -d office.techandtiny.com
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator webroot, Installer None
    Obtaining a new certificate
    Performing the following challenges:
    http-01 challenge for office.techandtiny.com
    Using the webroot path /home/office.techandtiny.com/public_html for all unmatched domains.
    Waiting for verification...
    Cleaning up challenges
    Failed authorization procedure. office.techandtiny.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://office.techandtiny.com/.well-known/acme-challenge/yF5zytN0pisE-NTOn3BHxc4R5YDfsgxUhYrrSobc8rw: "<!DOCTYPE html>\n\n 404 Not Found\r\n\n\n\n 404
    Not Found\r\n\n
    A possible workaround could be temporarily disabling the .htaccess file or Rewrite Rules if a first attempt is detected as failed and then reattempting a second time with the .htaccess with disabled. Just some food for thought.
  • You can also use a rewrite rule so that for Lets Encrypt verification request there is no redirection what so ever.
Sign In or Register to comment.
Support CyberPanel CyberPanel Discord

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!