I have created an instance of wordpress with open LiteSpeed cache in Digital Ocean droplets, it works fine if I have the IP configured in the Settings/General Site and Wordpress URL, but when I add my dns name, starts popping up 404 everywhere. The screen reads:
404
Not Found
The resource requested could not be found on this server!
Proudly powered by LiteSpeed Web Server
Please be advised that LiteSpeed Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.
I believe the problem is in this LiteSpeed, which don't seem to be clever enough to figure that there is a new domain configured? Unfortunately restarting the LiteSpeed web server did not help...
Any ideas?
You have to access the OpenLiteSpeed Console, you can find the password for the console in the .litespeed_password file in the root's home directory on the server.
You also need to allow your IP address to be able to connect to the console, you can do this simply by executing ufw allow from <your_home_ip_address>.
Also documented here: https://docs.litespeedtech.com/Cloud/wordpress/#web-server-control-panel-access
When you're within the Console you can go to "Listeners", here you'll find two listeners, one named "Default" and one named "Defaultssl".
On each listener you have to modify the "Virtual Host Mappings" to use your domain under "Domains" - after this restart OpenLiteSpeed, and it should no longer return a 404 when you access the site via your domain.
Related
I have a WordPress website[Bitnami Nginx sevrer] hosted on AWS ec2. I am facing this issue and cannot figure out what is causing it. There is one thing to note I am able to access my WordPress Admin Dashboard. I tried looking up online but all I find is "How to resolve Internal Server errors(HTTP 500)".
Here's what I have tried so far:-
Disabled all the active plugins on WordPress but I still face the same issue.
Tried to access the Nginx server logs but couldn't find anything there.
Also a couple of days back, I had modified WP_DEBUG to True in the wp-config PHP file and also specified my domain for the WP_HOME and WP_SITEURL parameters in the same file while hosting on my custom domain instead of using the Route 53 service. So could this issue be because of that?
I bought a domain from GoDaddy and hosting from another company. after completing method I logged in to my Cpanel and installed wordpress successfully.
After that, it give me two links one is for checking my website front end and the second one is for the backend. Now the problem is I can't access my website nor backend nor frontend both links show me the message
unexpectedly closed the connection.
How can I resolve this issue?
Firstly update domain name server. Hosting provider provide a hosting name server.
So please update name server than try.
Your both url working
I have a site hosted on 1&1 Ionos hosting. Purchased an SSL for the site from 1&1 Ionos as well. So let's say https://www.business.com/ is what I have. Then I have another another site say http://www.mycompany.com/ hosted at the same place - still waiting for my business SSL to be approved hence the http.
So I exported the database from business.com using plugin WP Migrated DB - setting the new URL and actual filepath.
Then I imported the database into a new database for my staging environment to be hosted at http://www.mycompany.com/clients/business.
I copied ALL the wordpress files for the site http://www.business.com/ into http://www.mycompany.com/clients/business exactly except I changed wp_config.php file to reflect the new database details. i.e username, database, location and password.
So I expected http://www.mycompany.com/clients/business to be a complete replica of the original https://www.business.com/. But when I browse to http://www.mycompany.com/clients/business I get the following error:
This site can’t provide a secure connection mycompany.com sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
I can't even login to the admin panel of http://www.mycompany.com/clients/business/wp-admin
Is what I tried even possible and if it is please tell me what I did wrong and how to fix it. I'd like to create a staging environment to test new themes and plugins before implementing on live environment. Critical to my original site is the aMember plugin which manages all the membership registration info. I've deleted the Really Simple SSL plugin folder from WP-Content/Plugins folder but the error remains.
Thanks in advance for any and all help and advice!
Step 1:
Check your .htaccess for rules enforcing https
Step 2:
Did you replace all links in the database? If not, you must search and replace all links from https://www.business.com/ to http://www.mycompany.com/
You can use a tool from: https://interconnectit.com/products/search-and-replace-for-wordpress-databases/comment-page-4/
Or just use command line wpcli (wp search-replace https://www.business.com http://www.mycompany.com
Step 3:
Open the new 'http://www.mycompany.com/' in a incognito tab. Browser caching might still redirect you to https.
I have a working blahblah.firebaseapp.com default domain working correctly. No problems there. My website was on another provider so I went through the process to connect it to firebase hosting. Everything went fine and the domain status in Firebase Hosting console shows connected for my blahblah.com and www.blahblah.com domains. My problem is that when I navigate to blahblah.com, I get a page that says
I can't find anyone with quite the same issue on Stackoverflow or any other site. There was one that was fixed by opening in a different browser (cached site issue), but this isn't my problem. I have double checked the DNS settings from my provider. Everything checks out. It's been close to 20 hours since I have completed the verification and the status shows connected in firebase hosting. I even re-deployed my site to firebase to see if that would reset something. Didn't help.
So now what should I do? Any ideas?
Assuming you initialized your project with default values, your public directory is what get's served. So, edit or add the index.html file in your public folder then firebase deploy. You should now be able to see your custom HTML.
I had also the same issue, experimented a bit and found the solution.
Case 1- You want your website to be served at subdomain.domain.tld as will as on domain.tld, but added only subdomain.domain.tld as custom domain on firebase hosting dashboard.
In this case the address domain.tld will throw an error.
To get rid of this error add another custom domain in your firebase
hosting dashboard as domain.tld
Case- 2- You want your website to be served over domain.tld but also accessible through subdomain.domain.tld
Add both the domains in custom domain field.
Edit subdomain.domain.tld to redirect at domain.tld.
Case- 3- You want your website to be served over subdomain.domain.tld but also accessible through domain.tld
Add both the domains in custom domain field.
Edit domain.tld to redirect at subdomain.domain.tld.
I have thoroughly reviewed both the Amazon Web Services documentation and many Stackoverflow posts related to my issue, but have not yet resolved it. My situation:
I have successfully set up:
an EC2 t2.micro instance with elastic IP, running Ubuntu 14.04.01 /
Apache2 / PHP / MySQL (LAMP)
WordPress 4.5 as a content management system
CiviCRM 4.1 as a constituent management app
I am able to access and run this configuration with the public DNS linked to the Elastic IP. I have a custom domain (mydomain.org) registered through Amazon Route 53 and have set up the necessary record sets (A, CNAME) to connect both mydomain.org and www.mydomain.org to the EIP. This configuration, accessed with HTTP, correctly serves the base page of the app, and I see what I expect from WordPress, with mydomain.org showing in the browser address window.
When I navigate to any other page, it breaks. I see the page, but the displayed URL is that of the EIP public DNS, not my custom domain. I suspect that rewriting the URL in the Virtual Hosts section of my provide a solution, but I haven't been able to determine the proper statements.
Further, I need to have this configuration support TLS / HTTPS. I have successfully obtained and installed the necessary certificates and set them up in my server configuration. I have edited the ssl.conf Virtual Hosts file, and have even been able, using HTTPS to successfully navigate to the base page of WordPress. It shows the basic HTML of the page, but all of the script driven formatting is missing. Again, navigating to any other page of the app breaks the TLS by using the EIP URL, not my custom URL.
I suspect the same solution to the initial issue will fix this issue, as well.
Thank you, in advance, for your advice and suggestions.
Bruce P pointed me in a good direction. I checked VirtualHosts in my .conf file; found it OK. Looked for httpd.conf without success, and reviewed my WordPress configuration, which is where I found the problem. The server information was not updated to reflect the changed URL. When I did that, all significant problems were resolved. Thanks, again, to Bruce P for pointing me in a good direction.
DVH