Skip to main content

Domain & SSL Issues

Appliku automatically provisions SSL certificates via Let's Encrypt for your custom domains. Most domain issues are related to DNS configuration or certificate issuance timing.

Common Issues​

SSL Certificate Not Issued​

After adding a custom domain, the SSL certificate may not be issued immediately.

Common causes:

  • DNS records have not propagated to the server yet
  • The domain's A record does not point to the correct server IP
  • Let's Encrypt rate limits have been hit (50 certificates per registered domain per week)
  • The domain was added before DNS was configured

Solutions:

  1. Verify that your domain's A record points to your Appliku server's IP address
  2. Wait for DNS propagation (can take up to 24-48 hours, but usually 5-30 minutes)
  3. If the domain was added before DNS was ready, delete the domain from Appliku and re-add it after DNS has propagated
  4. Check Let's Encrypt rate limits if you have been issuing many certificates
tip

You can verify DNS propagation by running dig +short yourdomain.com from a terminal. The output should show your Appliku server's IP address.

Domain Not Resolving​

Your domain shows a browser error like "This site can't be reached" or "DNS_PROBE_FINISHED_NXDOMAIN".

Solutions:

  1. Check that you have an A record pointing to your server's IP address at your DNS provider
  2. If using a subdomain (e.g., app.example.com), make sure the A record is for the subdomain, not the root domain
  3. Allow time for DNS propagation -- changes can take minutes to hours depending on your DNS provider and TTL settings
  4. Verify with nslookup yourdomain.com or dig yourdomain.com that the record resolves

"Connection Not Secure" Warning​

The browser shows a security warning when visiting your domain.

Common causes:

  • SSL certificate has not been issued yet (see above)
  • Certificate renewal failed
  • You are accessing the domain via IP address instead of the domain name

Solutions:

  1. Check whether the certificate was issued by visiting https://yourdomain.com and inspecting the certificate in your browser
  2. If the certificate expired, delete the domain from Appliku and re-add it to trigger a new certificate issuance
  3. Ensure your DNS still points to the correct server IP (it may have changed if you migrated servers)

Mixed Content Warnings​

The browser shows a warning that the page includes insecure (HTTP) resources on an HTTPS page.

Symptoms:

  • Padlock icon in the browser shows a warning
  • Browser console shows "Mixed Content" errors
  • Some resources (images, scripts, stylesheets) fail to load

Solutions:

  • Update your application to use HTTPS URLs for all resources, or use protocol-relative URLs (//example.com/image.png)
  • Set your application's base URL or site URL setting to use https://
  • For Django applications, set SECURE_SSL_REDIRECT = True and SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
  • For Node.js applications behind a proxy, trust the X-Forwarded-Proto header
note

Appliku's Nginx reverse proxy terminates SSL and forwards requests to your application over HTTP internally. Your application should check the X-Forwarded-Proto header to determine the original protocol.