Pardon what is likely a simple question. I have a clean install on a PI and just installed Wordpress with lighttpd. What do I need to change so that wordpress responds on a browser to http://RPi-IP (basically port 80 in place of the lighttpd generic page)?
I did bare metal minimal reinstall (technically a restore of a backup I made earlier) and installed WP from the dietpi-software optimizer again and oddly now going to the RPI’s IP only takes me to the WP install.
Different browser. Verified, restored a backup I made immediately after a minimal dietpi install. So it was clean and none of the proposed changes remain.
From the minimal install, I selected WP from dietpi-software and followed though, auto installing the webstack and selecting lighttpd. After that, going to 10.10.1.10 works correctly and takes me to the WP install.
UPDATE: Tried a different browser again and not working, back to default lighttpd placeholder.
I’m testing out an application of Cloudflare Zero Trust. When setting up the tunnel on the Cloudflare side, I need to be able to point to a device on my local network–in this case a Pi Zero W running WP for a very basic website. I can either point it to the Pi’s local IP for the tunnel, in which case it will default to Port 80 OR specify a port.
So, I either need to configure the webserver on the PI to serve the WP install on Port 80 or specific a different port to access the WP install.
How would I best go about doing this?
NOTE: I could run FuguHub as a test case, since it will install on the Pi Zero and defaults to Ports 80/443.
just to avoid a misunderstanding. All our web server apps will run on port 80 by default. What you are looking for is to remove / avoid the sub path to be added. But this has nothing to do with the port the web server is LISTEN on.