Fix Captive Portal Redirect from ".com" to ".net" -- 2

I need an experienced Linux/PHP/Apache network engineer to troubleshoot and fix a captive portal running on Ubuntu/Linux.

Issue:

- My captive portal was originally configured with hotspot.inetwall.com.
- I have migrated to hotspot.xxxxx.net because the ".com" domain has expired.
- I updated the configuration files, but users are still being redirected to the old ".com" domain, or the captive portal still references ".com" during the login/redirect process.
- I need the entire captive portal to use hotspot.xxxx.net only, with no remaining ".com" references.

Environment:

- Ubuntu/Linux server
- Apache
- PHP
- Custom Megacaptive captive portal
- Let's Encrypt SSL
- Hospitality Wi-Fi (HSIA)

Scope of Work:

- Find all remaining references to "hotspot solution".
- Check Apache virtual hosts, PHP code, configuration files, DNS, iptables, and captive portal redirect logic.
- Verify HTTPS certificates and virtual host configuration.
- Ensure all redirects and login URLs use "hotspot.inetwall.net".
- Test the complete captive portal login flow and confirm there are no references to the old ".com" domain.
- Document all changes made.

Required Skills:

- Linux system administration
- Apache, PHP, DNS, iptables
- Captive portal / hotspot gateway troubleshooting
- SSH remote troubleshooting experience

Remote SSH access will be provided. Please apply only if you have experience troubleshooting captive portals or hospitality Wi-Fi gateways.