Ok, I would not be the least bit surprised if the answer to my question exists somewhere already. I know next to nothing about so it's possible I've been searching the wrong terms. Here's my problem:
I'm trying to update a website that requires a secure connection (https). There's no development instance of the site so I've copied the site and the database to my local wampserver. When I try to browse the site locally I get an "Unable to connect - Firefox can't establish a connection to the server at localhost" error. I've done a bit of research and the version of apache I'm using is 2.2.22. According to the wampserver website this version does not have openssl. So I tried to update apache to v2.2.4. The update appeared to install just fine (there's an apache2.2.4 folder in c:\wamp\bin\apache), but I can't get my wampserver to switch over.
How can I move forward on this to create a self-signed certificate on my wampserver?
Related
I set up my SSL Perforce server with the official script on my Linux cloud vps. It's been fine but since I switched to 2022.1 P4V, I can't connect to it anymore. It says:
SSL connect to ssl:perforce.mydomain.xyz:16666 failed (An existing connection was forcibly
closed by the remote host. ).
Remove SSL protocol prefix from P4PORT or fix the TLS settings.
After a lot of digging... I found out that I can connect just fine if I replace the domain with the actual IP. And before that, when I was using 2021.1 P4V, I could connect using my domain name.
I tried generating SSL certificates with "CN=perforce.mydomain.xyz" (and a couple similar but different addresses like just mydomain.xyz) but it didn't work.
I think it's a thing in 2021.2 because another app I use just released a new version and updated their P4 plugin to 2021.2 P4API and it doesn't work with my domain name anymore...
Has anyone experienced this? Is it still possible to use ssl with domain name instead of IP with the latest clients?
I am using Webmin for my server control panel. I have bind DNS and setup Apache server for the domain URL. However whenever I go to the domain I will reach a Fortigate login page.
The question is I have never set any firewall to my server nor the router. How do I disable this and how can I actually get to the domain.
Please educate me if I said anything wrong. I am fresh new to server hosting. Thank you.
[EDIT]
The long story is, I install Ubuntu Server to my old desktop. I follow some random online guide to install LAMP stack, SSH and Webmin to the computer. After that I install a deb package from Dynu, a DNS service to the computer.
Then, I follow another online tutorial to point a domain to my server.
http://www.webune.com/forums/how-to-add-domain-in-webmin.html
This is the link to the tutorial. So when I finished the steps, I go to the domain and I found myself at a Fortigate login page. (I used Google Image reverse search to find out what it is as there isn't any logo)
The login page
What I am expecting from the domain is a Worpress installation page as I already upload the Wordpress files to the domain directory in the server.
The router that I am using is D'link DIR850L if it matters. All the firewall options had been turned off. The server is connected through this router.
I have a client site set up on AWS with multiple servers running HTPPS behind an Elastic Load Balancer. At some point, someone from the client's team attempted to update the SSL Cert by installing a new one directly on one of the servers (instead of in the ELB).
I was able to upload a new cert to the ELB, but when traffic is directed towards the server with the improperly installed cert, it triggers a security warning.
No one can seem to answer who attempted this install, how they went about, or where they installed it.
What's the best way to go about finding and removing it?
Thanks,
ty
If it's installed on the server, it has very little to do with AWS. I see you tagged the question with apache so I assume the server is running Apache Web Server. You will have to connect into that server and remove the SSL settings from the Apache Web Server configuration, just like you would with an Apache Web Server install anywhere else.
I'm using a Debian VPS on DreamHost and wanted to install a feature-rich customer issue-tracking system (not for software development like Bugzilla). OTRS made my shortlist and I followed the Installation Instructions through the "Web Server Configuration" step (/etc/init.d/apache2 restart), but the restart step reported failure. Nevertheless pgrep apache showed it was running. In fact, it turned out that although www.mysite/otrs/installer.pl was running, my regular website showed a page claiming it had no content (but when I looked in the website's folder, its content was fine, just not being served).
DreamHost Support was very helpful, but explained that they don't use the standard Debian Apache server for hosting websites and instead use their own. Specifically, the Debian server is in /etc/apache2, but the DreamHost server is in /dh/apache2. DreamHost Support determined that the OTRS installation instructions were configuring the usual Debian Apache location which somehow prioritized that server instead of the DreamHost server. They tried moving the otrs.conf file into /dh/apache2, but though the regular website was working again, the OTRS page wasn't.
Has anybody had success installing OTRS on a DreamHost VPS?
I've consulted one of our admins on this, and these are our suggestions:
You will either need to:
Adapt DreamHost's Apache build to incorporate the OTRS modifications
Get Debian Apache up and running
Both options will require an admin user and some knowledge of Linux command line and Apache management tools. You will also need to set your VPS to UNMANAGED, which means that any changes in the DH Web Panel to any of your domains will have no effect whatsoever. Just make sure the DNS records for any domains are pointing to your server. You will also need to be able to manage your own Apache configurations.
NOTE: This will also essentially mean that DreamHost support cannot and will not troubleshoot your domains. Unmanaged means unsupported in any way!
There are a few core differences between DreamHost's apache2 configuration and the default Debian build. The first issue I observe is that DreamHost's configuration does not allow for extra configuration files to be loaded in the manner that the OTRS documentation suggests. This means if choosing option 1, you will need to manually insert the OTRS directives into DreamHost's configuration files, which may prove difficult.
I would recommend moving or otherwise disabling the /dh folder entirely after setting your VPS to unmanaged. This will not allow DH-default Apache to start when the VPS starts. You may also need to remove the DH Apache startup script in /etc/rc3.d/S02httpd2 and the actual script at /etc/init.d/httpd2.
Once you have your own version of Apache running successfully, you might consider copying the VirtualHosts that were previously at /dh/apache2/apache2-ps/etc/httpd.conf into your own domain configuration files in your conf.d directory, or you can shuffle your website files around and configure your Apache to your desire.
Once you've got your own flavor of Apache running, you should be able to implement the OTRS instructions per their wiki. :)
I use mod_spdy to realize SPDY on apache. But I met some problems.
I did every step on ubuntu according to Google's document of installing mod_spdy.And I realized https on Apache. When I checked if mod_spdy has worked, I sent https request to the server, but I donot see server's domain listed in the "SPDY session" table that means the mod_spdy don't work. I also checked Apache server logs, and I didn't find any error message from mod_spdy.
I hope somebody can help me to deal with this problem.