Self hosted instance can't reach internet

[Rizwan-Basheer]

the main cobalt.tools instance working well but i when create my own instance first it working well after two days it stops working i reinstall it but it not works then i install it on other two different servers but it also not working on those servers i always get this response

{"status": "error",
"text": "i couldn't connect to the service api. maybe it's down, or cobalt got blocked. try again, but if error persists, check the <a class="text-backdrop link" href="https://status.cobalt.tools/\" target="_blank">status page or <a class="text-backdrop link" href="https://github.com/imputnet/cobalt\" target="_blank">create an issue on github."
}

[2shiraz]

Try using oAuth2 solution with new server IP

[Rizwan-Basheer]

i try oAuth2 but it not start working

[ihatespawn]

how did you create that instance

[wukko]

have you considered creating an issue using a clearly labeled template?

[wukko]

what links cause this error? can you give me more context?

[Rizwan-Basheer]

thats the video url "https://www.youtube.com/watch?v=6qIE4cR4Fqc" which is working on main instance but at my intances any urls including above url are not working.

i run this command in terminal "npm run token:youtube" then i open the url in other window and put the code and continue with a gmail account which is not important for me.

i create instances by git clone and my node version is 20.15.1

other services like soundcloud and reddit are working perfectly

[Rizwan-Basheer]

oh i found the problem before i using FREEBIND_CIDR=2a01:4f8::::/64 and the instance not works now i remove it try again now the instance start working
but how can i use FREEBIND_CIDR or force cobalt to use ipv6

[dumbmoron]

oh i found the problem before i using FREEBIND_CIDR=2a01:4f8::::/64 and the instance not works now i remove it try again now the instance start working but how can i use FREEBIND_CIDR or force cobalt to use ipv6

you can’t force cobalt to use ipv6. if you run cobalt in a docker container that has an ipv6 address, or directly on a server that has an ipv6 address, it will prefer using ipv6 and fallback to ipv4 only for services that don’t support it — but this is not a special feature of cobalt, it’s just how networking works.

[dumbmoron]

if you really want cobalt to only use ipv6, just ensure wherever you are running it has no ipv4 default route