I setup a droplet on digitalocean and pointed the domain to it. I have installed wordpress on the droplet (express setup), but I cannot figure out how to get it up and running. I can access a page without graphics when I type in the ip address of the domain, but when I try to go to the webpage, I get an error from Cloudflare which I installed on the previous instance of wordpress.
These are some of the screens:
Never mind. Figured it out. I had to change the IP on cloudflare to get to the right page.
Related
hope you can help me because I'm losing my mind here:
A couple of months ago, I started to build my new website (WordPress, hosted on Google Cloud, deployed with "Click to deploy" and I got the domain name on Google Domains).
Everything worked fine back then. But I needed to put this project on hold.
Now I wanted to continue working on the website, and I realized the VM was stopped. I successfully re-started it and wanted to access the WP back end with the link that can be found in the Deployment Manager of Google Clouds ([IP address]/wp-admin) but it doesn't work anymore. It only says the connection is not private, and I can't access the website. I can't even get to the login form.
What I have tried so far:
Changed ephemeral IP to static external IP & connected the VM to the IP
Pointed Domain toward static external IP - as shown in any tutorial
Updated NS on Google Domains
Created DNS Zones (A, CNAME)
Installed SSL for my domain successfull
Still not working, neither the IP nor the domain (server not found).
My guess - the Domain (mk-studios.net) is not live yet, and therefore, the SSL certification doesn't work yet. If not, I messed something up, and I don't know where to look. I don't get why it worked well months ago and has stopped working now.
Does anyone have a guess? Do you need any further details?
Thank you so much in advance,
Best,
Mario
This problem may have many causes but the most common is that your SSL has NOT installed properly. I suggest you the following steps:
Make sure that your SSL works fine and reinstall your SSL.
If you have access to DB, go to *_options table and in the first two rows siteurl && home you will find your URL. In this point remove the "S" from the https:// and make it http://.
If you have other server take the DB locally an connect with WP files from fresh installation.
Also when you remove the -s from https:// visit your url with incognito mode/private mode.
I will stay here to help you.
George
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.
I just recently moved my wordpress website from inmotion hosting to aws lightsail. I used all-in-one migration tool to migrate wordpress to new instance I created. I added DNS A-records, MX, TXT and CNAME. I changed nameservers on my Godaddy domain to point to it. If you go to greeksandscholars.store it shows up store I migrated. So my problem is that if I want to log in to my wordpress(on lightsail) I have to use the ip-address/wp-admin but if I try to use mydomain/wp-admin it sends me to my old wordpress site and I see the following screen.
when I login using domain/wp-admin
I tried to change the siteURL and homeURL but they show up greyed out. I have gone to wp-config to change it there but last time I did that it gave me a white blank screen. I am bit stumped at this point on what else I need to do to fix this issue.
When you add or update your DNS records it takes a couple of hours to reflect. Alternately I feel you may be forwarding your domain to an IP address.
I created a Windows 2016 Base EC2 Instance and installed IIS on it. But soon realized that I have to run WAMP to host PHP sites so I installed WAMP and stopped IIS service and everything was working fine.
Then I made a few changes to the site (It's a Wordpress site) and published it and since then the public IP is showing IIS page.
I have tried renamed iisstart.html to iisstart (to trick system into
thinking the file doesn't exist) from IIS folder but the public IP
is still showing IIS page.
I have tried restarting the instance machine. Localhost is showing my wordpress site but public/elastic IP shows IIS.
I have tried restarting WAMP, no luck.
I don't know how is it possible that IIS page is shown even when the file is renamed.
I have tried creating an Elastic IP as well but didn't worked.
Ok! So the issue is fixed! Now posting solution for anyone who will reach here (maybe my future self)
There was no issue with AWS EC2 or WAMP. The issue was in importing Wordpress.
When I imported Wordpress the Site Address and Wordpress Address changed to localhost. Due to which the IP was redirecting to localhost of destination machine.
Solution:
After you import your Wordpress, goto wp-admin -> Settings (in Side Bar)
And change the Site Address and Wordpress Address to the public/elastic IP of your instance.
Then clear Cache/Cookie on your destination machine and revisit the IP. It should work. (It did in my case)
I recently setup a wordpress website on IIS.
I configured the website and it is working on the local machine. I can browse pages and get to the wordpress admin.
I also configured IIS with the correct site binding, host name and ip address.
However from the internet I can not reach the website. It's as if the wordpress site is not listening to or IIS is not passing along traffic from the internet. And just to make sure it wasn't an issue with IIS. I setup a second website on that server that is accessible from the web. That one is working.
Any anyone has any ideas I'd appreciate it.
After doing some testing.
In this case. The wordpress site would not respond or map to the correct domain name on the main ip address of the server.
After adding a second IP address on the nic card and mapping that in IIS the website worked properly.
It was a very strange situation. It should of just worked on the main IP. But it didn't. shrug.