comfon
October 12, 2019, 9:50pm
1
I have installed an Ookla server which is litening on ports 8080 and 5060 via http. But when I call these ports by https I get an “self signed cert” error, and it seems that the browser try to read another cert on the server. I have to add that the https is working without problem.
https://speedtest.andels.net - works without problem
https://speedtest.andels.net:5060 - fails
https://speedtest.andels.net:8080 - fails
My domain is: speedtest.andels.net
I ran this command: certbot --apache
It produced this output: new cert was created then httpd and ooklaserver.sh restarted
My web server is (include version): Apache/2.4.29 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu server 18
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.39.0
Hi @comfon
looks like you have found a solution.
Two hours earlier, there were checks of your domain and port 8080 - https://check-your-website.server-daten.de/?q=speedtest.andels.net - there was a self signed certificate with version 1 and serial number 01, Firefox had a curious error.
Now checked with my browser, port 8080 has a working certificate, rerun the test - now it's ok.
PS: Port 8080 is checked, so you don't need add the explicit port 8080.
And Ookla supports two protocols on one port, so port 8080 works with http and https:
So you don't need two different ports (may be Ookla want's that).
comfon
October 12, 2019, 11:15pm
3
Yes thanks, I found a solution after reading one of your topics here.
I do not know yet how to make port 8080 to use only https. I tried to redirect the http in the apache conf:
“Redirect permanent / https://speedtest.andels.net/ ” and everything looks fine but ookla test cannot find: http://speedtest.andels.net/crossdomain.xml as it changes to https://speedtest.andels.netcrossdomain.xml (the / is removed).
Your redirect rule is wrong.
Check the output of your main domain (without the port specified - https://check-your-website.server-daten.de/?q=speedtest.andels.net ):
Your first redirect - there is no / at the end.
So if a file or subdirectory is redirected, a new domain name is checked -> that domain doesn't exist.
Check some Grade E - and other Grade C - results, there are redirect rules.
comfon
October 13, 2019, 12:11pm
5
Thank you very much Juergen,
I added an / at the ende of the DocumentRoot path and I think it is working now.
1 Like
system
Closed
November 12, 2019, 12:11pm
6
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.