native ginkgo
I wanted to report a weird issue with the Bing Endpoint. I tried to use the Config Token option, but it's not there anymore. I swear I saw it all the time yesterday. I've tried incognito mode and restarting the docker instance serveral times, and one time PC as well (it's been a day), but the issue persists.
Could you please let me know if you know what's going on?
Yes, Modified my env file carefully.
Thanks a lot for your patience and willingness to help in advance!
native ginkgo
Update: Solved. Simply run docker builder prune to purge cache and rebuild it.
Update 2: Occured again after a few days, tried same solution, didn't work this time.
white oxide
@native ginkgo
if that worked the first time, try:
npm run update:docker
then:
docker-compose up
native ginkgo
<@456226577798135808>
if that worked the first time, try:
`npm run update:docke...
aaaaand nope, didn't work
i put entire cookie
yeah the config button appeared
but
seems like the cookie is being rejected?
white oxide
i put entire cookie
I've had the null error happen to me twice, it fixed itself after a couple of hours both times
native ginkgo
I've had the null error happen to me twice, it fixed itself after a couple of ho...
should i try another cookie orr
white oxide
when it happenned to me nothing worked, I had to wait 6 hours once and 1 hour another time. It just started working by itself after a little while. I have now idea what is causing that 🤷♂️
there was another thread about that same error: https://discord.com/channels/1086345563026489514/1143923363694260356