When adding an addon domain, the addon usually results in 404. Run into this on two different clusters running similar setups with enterprise litespeed.
To fix is easy enough, I'll just add another domain and then delete it, and then the other addon domain will start working. Easy to fix real quick, but still annoying. I'm guessing by deleting a addon domain it's causing the records for the other add-ons to get activated in litespeed, or something. The vhost? Idk, I haven't really looked into it since it's a minor annoyance.
Steps to reproduce:
- Add new addon domain.
- Install WP app.
- Go to the site, it's 404.
To fix:
- Add a new addon domain.
- Delete that new addon domain.
Not sure if I left it for a while if the addon domain would self resolve, maybe LS would self resolve it after a while, maybe after it's next restart, idk. Just tossing this out into the void as fyi lol
