@w0051977 after re-reading this issue, I started thinking of something that could be the actual issue; your “domain name”.
Please note: I always work on Windows, so I could be wrong in some or all areas. I’m trying to use my best guess work here.
During my test environments (local), I always have a top-level domain name, e.g. ianscomputer.internal. While I was learning WP, I had some difficulties because I was using only localhost. Honestly, I didn’t take the time to learn why, so I just created a fake “full domain name” and moved on.
Based on the stated above, I did a quick Google search and came across this post: Faking a top-level domain name for local development with Apache which says:
Not every CMS (looking at you WordPress!) has relative paths to their content.
So I would say:
- Follow the steps to create a fake top-level domain. (Super guess x3)
- Check Apache settings as suggested on this post: [How to trace Apache 301 Moved Permanently?]https://serverfault.com/questions/361165/how-to-trace-apache-301-moved-permanently.
- Get rid of the :80 in all settings. When using http:// before the domain, this is stated. (Personal opinion)
- While testing, change your permalink structure to Default. It will make your troubleshooting easier. (Personal opinion)
Test the above and let us know what works and does not work.
I hope this helps and good luck.