Wordpress changing site URL on RaspberryPi -- using Nginx Proxy Manager - wordpress

I have a RaspberryPi running Wordpress on my internal home network (DietPi, lighttpd). I can access WordPress at home by typing http://192.168.1.2/wordpress on my browser.
I have a domain name e.g. example.com, my DNS redirects that to my home router. I have another RaspberryPi running Nginx Proxy Manager. This manages my Letsencrypt SSL certificates and should allow me to access the Wordpress site outside my network.
I get a 404 error. I changed the SITE URL to example.com (using http://192.168.1.2/wordpress/wp-admin/options-general.php). Still no joy. I tried copying index.php to the /var/www. Still no joy. I followed this guide, and it does not work https://wordpress.org/support/article/changing-the-site-url/.
I revert to http://192.168.1.2/wordpress, and things work. What and I doing wrong?

Related

Ghost blog https issue when hosting in subdirectory on a separate server via Nginx proxy pass

I'm an amateur here. So my blog set up is:
Root site on one droplet: example.com, SSL via Let's Encrypt
Ghost blog hosted as subdirectory, i.e. example.com/blog, on a separate droplet
On main server's Nginx config, location /blog/ is directed the blog server's IP and port 2368 via proxy pass
It was working for quite a while until it is not 😅 Somehow the Ghost config file corrupted (completely emptied), and Ghost could not run. As it was still on Ghost 3, so decided to do a clean migration on a new one-click droplet with Ghost 5.
I had all posts exported before and Ghost/content/images all backed up.
The new site imported content seems fine. But I could not get the HTTPS working. The root site is on HTTPS and loads the blog page fine, but all posts are requesting images via http - which won't work and gives Mixed Content error. Something like:
Mixed Content: The page at 'https://www.example.com/blog/post-title/' was loaded over HTTPS, but requested an insecure image 'http://www.example.com/blog/content/images/size/route-to-image.jpg'. This request has been blocked; the content must be served over HTTPS.
Any idea? I also noticed that after migration I have to proxy pass to just the IP rather than IP + port 2368 to actually make the site work.
I have tried Ghost setup SSL but it gave errors.
In Ghost admin panel, all images show up fine even it's still requesting via http.

Proxing ghost blog as subpage /blog from digitalocean on external server using nginx

I would like to redirect my ghost blog on my other website to achieve ghost blog displaying like this: https://kasacja-aut.pl/blog
Host where the website is stored: https://dhosting.pl/
The server of this domain doesn't support the Node.js, ghost is set up correctly on digitalocean and running but I don't know if the nginx configuration is set correctly.
The domain:https://kasacja-aut.pl is actually proxied via cloudflare and I thinking if I should add any DNS records to it? Beacuse I didn't add any.
Nginx configuration on digitalocean
Thanks in advance.

Wordpress with LiteSpeed shows 404 when trying to access it by my new domain

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.

Work on a Wordpress site in Plesk before DNS is pointed

I've installed Wordpress on a 'subscription' in Plesk (latest version) on my server. The domain related to the subscription is not currently pointed to my server. However, I'd like to work on the Wordpress admin area before I point the domain.
Can this be done? At the moment if I use the 'login' button on the domain in Plesk it redirects me to the actual domain. Which as I say isn't currently pointed so gives me an error.
Can I access the website via the server and the directory folder of the site?
Thank you
You can update your hosts file to map the domain to the IP address of your server.
If the domain were example.com and the IP address of your server was 111.111.111.111 you would just need to add the line:
111.111.111.111 example.com
You can find where your hosts file is located here.

Drupal Multisite, MAMP and SVN Best Practices?

I successfully set-up Drupal Multisites with:
site1.domain.com
site2.domain.com
site3.domain.com
using Virtualhosts and editing the etc/hosts with MAMP on my localhost. I then deployed it using SVN (it deploys automatically) on the live site.
The Problem: when I type "Site1.domain.com" because it goes to my localhost instead of my live site. Is there anyway to avoid this? (apart from renaming the subdomain, because it speeds up deployment)
Just check your virtual host settings in httpd.conf file, are you using IP address to redirect them?
And if its directing to your localhost, just check your host file, if might be redirecting because of that

Resources