Hello Everyone,
We have an on-premises commcare instance that was already working, but we changed the public IP and restarted our servers, then we encountered an issue on formplayer that we can't seem to resolve
can you help us please
Hi Mirado
Have you tried using curl or wget from the command-line to make sure that your formplayer machine can still access the CommCare host?
Perhaps there is a firewall rule or something else that is preventing connections to the new IP?
Hello Simon,
Indeed, it's OK now, I had to put a nat hairpin on the router
Thank you so much
1 Like
If the issue started immediately after changing the public IP and rebooting the servers, then it’s very likely something in the Formplayer/CommCare service configuration is still pointing to the old address or hostname.
check things like:
-
nginx / reverse proxy config
-
COMMCARE_URL or related environment variables
-
DNS records
-
SSL certificates
-
firewall rules / allowed hosts
-
whether Formplayer can still properly reach CouchDB/Postgres/Redis internally
A lot of the time after IP changes, one internal service is still trying to communicate with the old endpoint and Formplayer tends to fail in slightly confusing ways because of that.
I also ran into something vaguely similar once after changing router/network settings on a self-hosted setup and it turned out to be DNS/routing related rather than the app itself.