The community member published a Docker container on their local network and linked a DNS, but their bot is presenting errors due to referencing the local IP address. Even after publishing the bot, the link in "Your typebot link" still shows the local IP address. The community member updated the URLs in the .env file and rebuilt the Docker images, but is unsure if there is any reference to the local IP address in the database.
In the comments, another community member suggests checking the NEXT_PUBLIC_VIEWER_URL setting, which should hold the domain, not the IP address. Another community member believes the issue could be related to caching, as they were able to access the correct address after a while, even after destroying and recreating the containers.
Guys, I did some tests by publishing a docker on my local network.
Now I linked a DNS and wanted to send my bot to some friends to see. The viewer is working, the builder is working too, but the bot presents errors due to referencing the local IP of the network.
Even after publishing a bot, the link presented in "Your typebot link" presents the local IP for access.
The only thing I did was update the URLs in the .env and rebuild my docker images. Is there any reference in the database?
@Baptiste It was correct, I believe it could be something related to the cache. I did a SQL dump of the database and didn't find anything that referenced it.
The strange thing is that I tried to log in to the anonymous tab and it still showed up, all this after I destroyed the containers and recreated them. After a while I accessed it again and the address was correct. I honestly didn't understand why, but now it's ok.