admin wrote
The refresh-solves-the-problem behavior suggests that this probably a timeout issue. Do you experience error 505 immediately after visiting the URL the first time or does it show up after a few seconds (or even 30 seconds?)
First, the Xampp server is no longer running any SSL. I plan to bring that back into the mix later on. For now I'm just analyzing the current behaviors.
505 error occurs instantly after first click, then usually not at all after refresh, however sometimes it takes a couple to a few refreshes to clear up. At the moment I'm suspecting it is possible that packets are being lost or corrupted. I know this is not the optimum set up but both the Abyss host and Xampp hosts are running over WAN. I do plan to at least run ethernet to the Abyss host soon.
For the Xampp server that isn't necessary right now since the app I'm running is only for personal use. Also I am the primary user of that system, which lives presently on my laptop which is my primary computer anyway so I can always access it directly. Future plans are to migrate it over to another Windows machine so my whole family can access it wherever they are. At that time they will both be over LAN only and (perhaps) that will solve the issue entirely.