Today after 12:00 GMT+3 tiktok.com stopped resolving on all of my servers (Netherlands, Germany) and my own computer using cloudflare/google DNS. Meanwhile www.tiktok.com works fine everywhere. I suggest to switch to www.tiktok.com instead.
TypeError: fetch failed
at node:internal/deps/undici/undici:12502:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async default (file:///home/acid/cobalt/api/src/processing/services/tiktok.js:39:18)
at async default (file:///home/acid/cobalt/api/src/processing/match.js:129:21)
at async file:///home/acid/cobalt/api/src/core/api.js:254:28 {
[cause]: Error: getaddrinfo ENOTFOUND tiktok.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'tiktok.com'
}
}
reproduction steps
Use Cloudflare (1.1.1.1) or Google DNS (8.8.8.8)
screenshots
links
platform information
Docker on Debian GNU/Linux, Docker on Ubuntu 22.10, Docker on Linux Mint
additional context
No response
Originally created by @sertraline on GitHub (Jan 18, 2025).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/1057
### bug description
Today after 12:00 GMT+3 `tiktok.com` stopped resolving on all of my servers (Netherlands, Germany) and my own computer using cloudflare/google DNS. Meanwhile `www.tiktok.com` works fine everywhere. I suggest to switch to `www.tiktok.com` instead.
```
TypeError: fetch failed
at node:internal/deps/undici/undici:12502:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async default (file:///home/acid/cobalt/api/src/processing/services/tiktok.js:39:18)
at async default (file:///home/acid/cobalt/api/src/processing/match.js:129:21)
at async file:///home/acid/cobalt/api/src/core/api.js:254:28 {
[cause]: Error: getaddrinfo ENOTFOUND tiktok.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'tiktok.com'
}
}
```
### reproduction steps
1. Use Cloudflare (1.1.1.1) or Google DNS (8.8.8.8)
### screenshots
### links
```shell
```
### platform information
Docker on Debian GNU/Linux, Docker on Ubuntu 22.10, Docker on Linux Mint
### additional context
_No response_
GiteaMirror
added the bug label 2026-08-10 18:02:35 -05:00
<!-- gh-comment-id:2599668789 -->
@wukko commented on GitHub (Jan 18, 2025):
we're already aware that tiktok blew up its DNS records, it's not a cobalt bug:
https://x.com/uwukko/status/1880567802798682501
<img width="531" alt="Image" src="https://github.com/user-attachments/assets/75ea5b6d-e1f9-4685-883f-d3a954894ae9" />
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @sertraline on GitHub (Jan 18, 2025).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/1057
bug description
Today after 12:00 GMT+3
tiktok.comstopped resolving on all of my servers (Netherlands, Germany) and my own computer using cloudflare/google DNS. Meanwhilewww.tiktok.comworks fine everywhere. I suggest to switch towww.tiktok.cominstead.reproduction steps
screenshots
links
platform information
Docker on Debian GNU/Linux, Docker on Ubuntu 22.10, Docker on Linux Mint
additional context
No response
@wukko commented on GitHub (Jan 18, 2025):
we're already aware that tiktok blew up its DNS records, it's not a cobalt bug:
https://x.com/uwukko/status/1880567802798682501