http://192.168.1.175/nextcloud (WORKS)
https://192.168.1.175/nextcloud (BROKEN w/"SSL_ERROR_RX_RECORD_TOO_LONG" message)
http://[domain].allowed.org/nextcloud/login (WORKS)
https://[domain].allowed.org/nextcloud/login (BROKEN w/"SSL_ERROR_RX_RECORD_TOO_LONG" message)
Both HTTP and HTTPS fail via WAN. HTTP times out while HTTPS gives the same "SSL_ERROR_RX_RECORD_TOO_LONG" error message.
I'm using FreeDNS for multiple sites I host and the others work fine. I have forwarded both ports 80 and 443 to 192.168.1.175 on my firewall. Port 80 shows up as stealth on ShieldsUp, while 443 shows up as open.
When running Let's Encrypt, I received a message of:
Code: Select all
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for [domain].allowed.org
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. [domain].allowed.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://[domain].allowed.org/.well-known/acme-challenge/[challenge code]: Timeout during connect (likely firewall problem)
I assume I have something messed up in one or more (apache2?) conf files, but I don't know enough to figure it out on my own.
I think this is the only one I tried modifying:
Code: Select all
root@DietPiNextCloud:/etc/apache2/sites-available# more 000-default.conf
<VirtualHost *:80>
ServerName [domain].allowed.org
ServerAdmin webmaster@localhost
DocumentRoot /var/www
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
ErrorLog ${APACHE_LOG_DIR}/error.log
#CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>