I am currently trying to install a self-signed SSL certificate on a wamp server (running apache 2.4.2).
I have almost word for word followed this answer to do so.
When trying to connect via https:// on chrome it nearly always fails, returning ERR_CONNECTION_CLOSED or ERR_CONNECTION_ABORTED but if you keep refreshing, it will sometimes connect as expected (though only 1 in 20 at best...)
I'm not particularly experienced with any of this, but if anyone can point me in the direction of something I may be doing wrong then that would be much appreciated!
If your server is up and you are able to browse the website with http:// then you need to check if the port 443 is open or not. Also, if you have proxy, firewall and load balancer then you need to check that port 443 is open on the same
Related
In the documentation for icecast 2.4.2 I see the following about ssl.
ssl If set to 1 will enable HTTPS on this listen-socket. Icecast must
have been compiled against openSSL to be able to do so.
However this wording is unclear to me whether or not the ssl is forced for this port or not? I am wondering this because we are running into an issue where safari is forcing ssl redirect and we want to keep the server listening on both ssl and non-ssl on the same port ( if thats possible )
Another thing is that it says it must be compiled against openSSL but we are installing it from apt in xenial. Does this mean its default to ssl?
Thanks~!
However this wording is unclear to me whether or not the ssl is forced for this port or not?
On that particular socket, it is. A server bound to that socket cannot support HTTPS and non-HTTPS at the same time. Usually, you'll use port 80 for HTTP and port 443 for HTTPS.
Note that you can have multiple sockets bound to Icecast, simply by putting in multiple <listen-socket> sections. It's common to serve both HTTP and HTTPS this way.
I am wondering this because we are running into an issue where safari is forcing ssl redirect
Your server configuration is irrelevant here. Icecast will not redirect HTTP requests to HTTPS. It's possible that you hit the stream on HTTPS once and that Safari cached this. It's also possible that you turned on HSTS or something for your domain. You would have to debug this with a tool like Fiddler.
and we want to keep the server listening on both ssl and non-ssl on the same port
You say "keep the server listening"... that's not possible. If it appears you're set up this way today, that's not accurate.
In a sense it does. Icecast if you are using it as its own server will not resolve the enabled ssl port unless its https://.
You also cannot use the same port for both ssl and non-ssl.
Finally the xenial ubuntu package also is not compiled for ssl.
SSH files (https://) not working in ipv6 enabled droplet.
We using Comodo PositiveSSL files. Once we remove the ssl files it's works fine with http://
Error that shows in website is,
This site can’t be reached www.website.com refused to connect.
ERR_CONNECTION_REFUSED
Any thoughts would be greatly appreciated and DO community support not able to cover this much technical info so please I appreciate your feedback.
Thanks!
I think the problem is not with your SSL , the port on which your site is running on HTTPS is not opened on the network , and may be that's causing the issue . Try the same website on HTTPS from a normal internet connection (That means outside your work network, if you are inside a one ) and if it works ,then you need to open the port on which your site is running on HTTPS . Or if you are sure that your port is accessible, then try to clear browser cache and retry . Let me know if that helps :)
I have successfully added SSL certificate to my url. now url is "https://puinex5xgm-l1". Its working fine on browser. but whenever I try to add port to this ulr "https://puinex5xgm-l1:90/" its giving me "SSL connection error ERR_SSL_PROTOCOL_ERROR". My apache server is running on port 90.
While creating certificate I have used domain name as "puinex5xgm-l1".
Please help.
ERR_SSL_PROTOCOL_ERROR is not related to the certificate. My guess is that you don't have https on port 90 enabled but instead plain http, which then will cause such an error.
I have found the solution.
I have made changes in "httpd-ssl.conf" file. Here, I have used "VirtualHost default:90" instead of "VirtualHost default:443".
Now Apache server listening my port.
Its working fine now.
I'm running apache on an AWS server and I have an issue that I can't find any answers to. Normally I'd trawl through this site until something similar crops up and work with that but I can find literally nothing on this:
Apache 2.4 running on AWS Windows 2012
Listening on port 443 correctly
Everything works fine
Something goes wrong.
Apache cannot be accessed outside of the server
Apache is available locally on port 443
Apache is still listening on port 443
No new TCP connections are being established to the server from the outside world.
With the above information, anyone would think that the issue is with the AWS server but it isn't..
Bouncing the Apache 2.4 service on the AWS server corrects the issue and allows connections in from the outside world.
I'd really appreciate some help with this one.. it's been driving me crazy!
Thanks
Will
I already installed Tomcat server while developing my java web app. But I also needed to get access to my database using PHPMyAdmin and install MySQL as well, so I downloaded XAMPP. I cannot disable apache server since I already have Tomcat. Now my struggle is, I cannot open
"localhost:8080" which was my original port. It's now replaced with simply "localhost".
Can you help me fix this error? THANK YOU :D
Sounds like you now have:
Tomcat serving traffic on port 8080, as it always has (at http://localhost:8080)
Apache/XAMPP serving traffic on port 80 (at http://localhost, obviously with the port missing since 80 is the default http port)
Assuming that's the case, you don't have a problem. Serving http traffic from different ports on the same host is not an issue.