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.
Related
The title is quite descriptive, I bought a domain using Google Domains. I mount an Apache Server 2.4 in Windows 7. The problem is when i access the web url it shows the ip instead of the URL. I asked Google for this problem and they referred me to Apache configuration. But i don't find nothing in the Apache configuration to show the URL instead of the IP. Anyone can help?
I already solved. The problem was in Google Domain configuration in the DNS configuration. Ask Google they are really kind if you have the same issue.
I have two Wordpress websites hosted on two different servers and wish to consolidate these to be hosted on one server.
I've successfully transferred the database and website files over and setup the new virtual host in Apache.
Before switching the DNS over to the new server, I like to confirm it is working by altering my hosts file (I'm on Windows) to point to the new server:
xxx.xxx.xxx.xxx example.co.nz
I can verify this by running ping example.co.nz and see that it is correctly pinging the IP address specified in the hosts file.
The strange thing, though, is that when I go to example.co.nz in my browser, I am redirected and served the other website that was originally on this server; othersite.co.nz.
But if I open my Chrome Dev Tools, which has the cache disabled, then I am served the correct site.
Is this just a local caching issue or will other users trying to access the site be affected by this? Is there a way I can verify this, perhaps externally?
I was running my webserver on Plesk platform before moving to CPanel due to my perceived perception of Plesk's over-sensibility to threats to security.
After the migration, my site runs quite alright but a sister site that has my IP in its A records couldn't connect through me anymore. It only brings a default website CGI page. Please, I need help.
Have you created your second site on your cPanel server ? If yes, then there is an issues with the IP, Please check your domain IP and httpd configuration file on cPanel server and try update that IP in your DNS zone which are you using on cPanel server. Most of the time this type of issues occur due to wrong IP.
All i did was to create a wildcard subdomain which was attached to the subdomain already created on the other server i was trying to point to. That did the magic. Sorry my response seems belated.
I'am quite new to setting up and managing websites, domains and stuff.
I purchased a domain (let's say example.de) and registerd it on my vserver running Parallels Plesk. As I need secure access I requested and created a SSL-Certificate at startssl.com. The developed application (Spring-Boot) runs on an EC2-Instance at AWS. The Product-Website runs on an Apache-Webserver on an EC2 instance. I need to secure both, the App (app.example.de) and the Website (example.de) using SSL.
What I want to archive is a redirect from the domain https://example.de to the EC2 Instance. I already tried several things - some I remember from the try&error marathon
Configure Plesk frame-forwarding the traffic on https://example.de to the ec2-ip
Obviously the Browser warns me that the Certificate is issued for example.de and not for and classifies the traffic as unsecure. Same like when accessing it like https://...
I also uploaded the certificate at Plesk - Also without success
Is there a solution for my setup? Or do I need (or is it recommened) to use Amazon Route53 for that task? Would be nice if someone could guide me and provide some tipps as I am pretty new to this topics.
Thanks
It seems there is no way around AWS route 53.
I figured out that there is a Extension for Plesk that is designed to route traffic using route53 and even a nice manual article at the Plesk homepage how to use any external DNS and also Route53 Extension. As this Extension requires a newer version of Plesk, than that one I am using I wasn't able to install it. I am pretty much bound to this version, so an update didn't come into question. I cannot tell for sure if using this Extension solves my initial problem, but it seems to be a potential solution.
The most simplistic solution (at least for me):
I ended up moving my Domain the AWS, created a Hosted-Zone, Added a Record Set with the IP of the EC2 and the DNS Server provided due the hosted Zone. Everything is now working like a charm.
Some more Background: The Product-Website and App-Frontend are running inside an Apache where I installed mod_ssl and configured SSL access. The Application backend runs as a Spring-Boot-App in a Tomcat where I also configured SSL using a TomcatConnectorCustomizer.
This setup works for my scenario
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?