+- ASK NC (https://ask.nascompares.com)
+-- Forum: Q&A (https://ask.nascompares.com/forumdisplay.php?fid=1)
+--- Forum: Before you buy Q&A (https://ask.nascompares.com/forumdisplay.php?fid=2)
+--- Thread: Asustor running NextCloud (/showthread.php?tid=11811)
Asustor running NextCloud - Enquiries - 03-14-2025
I Team.
Watched all your videos on Asustor nas and finally got my self a Asustor lockerstore 2 / AS6602t
I changed the nas port form 8000 to 81 for http connections and port 8001 to port 444 for https connections and Enabled Automatic change HTTP connections to HTTPS Connections.
I installed NextCloud on the nas and enabled EZ-Connect.
NextCloud runs under port : 32680
I can login to my nas remotely but keep getting the certificate error when browsing to my external nas url.
Does the certificate only work on port 443 ?
Or I'm I doing something wrong perhaps ?
I would like to use NextCloud as a file share to 7 users using then NextCloud Files option but at this point I cant secure the https connection with EZ-connect.
Thanks for all the informative videos. You helped me allot in understanding how a Nas works with your great videos on Youtube.
Thank you in Advance
Kind Regards
Riaan van Vuuren
South Africa
RE: Asustor running NextCloud - ed - 03-14-2025
Yes, the SSL certificate typically works only on port 443 by default, as it's the standard port for HTTPS. However, Asustor’s EZ-Connect and custom ports can sometimes cause issues with SSL validation.
Possible Reasons for the Certificate Error:
Port 444 Instead of 443
Many SSL certificates are bound to port 443 by default. If you're running HTTPS on port 444, browsers may flag it as insecure.
Some certificate authorities only issue valid certificates for port 443.
Self-Signed Certificate Warning
If you're using the default self-signed certificate from Asustor, browsers will always show a security warning.
To fix this, you need a trusted SSL certificate from Let's Encrypt or another provider.
NextCloud Running on Port 32680
Your NextCloud is running on port 32680, but if the SSL certificate is tied to port 443, it won’t cover this port.
If you’re accessing NextCloud via https://yourdomain.com:32680, the browser might not recognize the SSL certificate.
Solutions & Fixes
✅ 1. Force HTTPS Through Reverse Proxy (Recommended)
Instead of running NextCloud on port 32680, set up a reverse proxy on the NAS to route https://yourdomain.com/nextcloud to localhost:32680.
On your Asustor NAS:
Go to ADM Control Panel > Reverse Proxy.
Create a new rule:
Source: https://yourdomain.com
Destination: localhost:32680
Ensure HTTPS is enabled for the source.
✅ 2. Use Port 443 for HTTPS
Try switching back to port 443 for HTTPS in Asustor’s settings.
Test your connection using https://yourdomain.com without specifying a port.
✅ 3. Get a Valid SSL Certificate
If you’re using a self-signed certificate, install a Let's Encrypt certificate in ADM > Certificate Manager.
Make sure to set it as default and use it for all services.
✅ 4. Configure NextCloud’s Trusted Domains
If NextCloud is rejecting your HTTPS connection, add your domain to its config:
SSH into your NAS.
Edit config.php (/volume1/.@plugins/AppCentral/nextcloud/config/config.php).
Add your external domain under trusted domains:
php
Copy
Edit
'trusted_domains' => array (
0 => 'localhost',
1 => 'yourdomain.com',
2 => 'your.external.ip',
),
Restart NextCloud.
Final Steps
Try accessing NextCloud via https://yourdomain.com/nextcloud (without a port number).
If the issue persists, check browser console logs and run:
bash
Copy
Edit
sudo openssl s_client -connect yourdomain.com:32680
to debug SSL issues.