TypeError: fetch failed
at node:internal/deps/undici/undici:13484:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: ConnectTimeoutError: Connect Timeout Error
at onConnectTimeout (/home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:190:24)
at /home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:133:46
at Immediate._onImmediate (/home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:174:9)
at process.processImmediate (node:internal/timers:511:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
} Promise {
<rejected> TypeError: fetch failed
at node:internal/deps/undici/undici:13484:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[cause]: ConnectTimeoutError: Connect Timeout Error
at onConnectTimeout (/home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:190:24)
at /home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:133:46
at Immediate._onImmediate (/home/iperona/DiscordBot/Wolvesville/node_modules/undici/lib/core/connect.js:174:9)
at process.processImmediate (node:internal/timers:511:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}
}
Hi, none of the files or services you mentioned exist on my server.
Ok.
What do you have in /etc/resolv.conf?
First of all, check whether you have the file
/var/run/systemd/resolve/resolv.conf
If you do not have that file, then your Plesk instance has not been installed properly.
If you do have that file, then you are missing a symlink (the file /etc/resolv.conf is a symlink to aforementioned file).
Either way, it is best to reinstall the system - it is very likely that you have lots of files that are missing (even though they should be there).
Please note that reinstallation is best done after adding a correct /etc/resolv.conf file.
Also note that you can manually change the /etc/resolv.conf file to contain Google Resolvers - this might be handy if the resolvers of your hosting provider somehow do not work properly (and please do not forget that the Google Resolvers are a temporary workaround, not a permanent fix!)
Kind regards....
Both /etc/resolv.conf and /var/run/systemd/resolve/resolv.conf are empty
nameserver 1.1.1.1
nameserver 8.8.8.8
ls -l /etc/resolv.conf
~# resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Current DNS Server: 8.8.8.8
DNS Servers: 8.8.8.8 1.1.1.1
Link 2 (eno2)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (eno1)
Current Scopes: DNS
Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 81.169.163.106
DNS Servers: 81.169.163.106 85.214.7.22 212.227.123.16 212.227.123.17
DNS Domain: stratoserver.net
@trialotto
Hi, it seems that this service was uninstalled, by running "apt install systemd-resolved" it was reinstalled and I can now access the file.