Error 503 when installing node-red/Node.js

General
1

I am having difficulties upgrading my node-red installation. The following command (and others) all return a 503 Error when run:
Running Node-RED install for user pi at /home/pi on raspbian
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node18
with this result:
This can take 20-30 minutes on the slower Pi versions - please wait.

Stop Node-RED :heavy_check_mark:
Remove old version of Node-RED :heavy_check_mark:
Remove old version of Node.js :heavy_check_mark: v10.24.0
curl: (22) The requested URL returned error: 503

updates using apt also fail. The system is a Pi 4B running Buster

2

With the same error? That suggests there is a problem with the pi apt repository. Show us what the command
sudo apt update
gives.

3

here's the apt command:
sudo apt update
Hit:1 https://repos.influxdata.com/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://apt.grafana.com stable InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Err:5 https://deb.nodesource.com/node_18.x nodistro InRelease
503 Service Unavailable [IP: 143.204.15.127 443]
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
W: Failed to fetch https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease 503 Service Unavailable [IP: 143.204.15.127 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

4

Can you open that in a browser? It is ok for me at the moment, so there is not a problem with the server.
Can you ping the server?
ping deb.nodesource.com

Edit: Obviously you can ping it, otherwise you would not get the 503 error.

5

using chromium on pi 4 in question returns:
503 Service Temporarily Unavailable

on another linux box running mint 21 (and firefox):

works OK.

ping deb.nodesource.com works OK on both machines

6

Are they on the same local network?

Are you on a company network? If so then I suspect it is something on the network.

7

they at both on my home LAN.

8

Connected to the same router the same way? Wired/wifi?

9

both ethernet wired to the same router

10

here's what nslookup shows for both machines:
from the linux mint 21 box:

nslookup deb.nodesource.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
deb.nodesource.com canonical name = deb.nodesource.com.cdn.cloudflare.net.
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.5.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.4.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 172.67.10.205
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:41a
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::ac43:acd
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:51a

from the pi4:
pi@pihome:~ $ nslookup deb.nodesource.com
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
deb.nodesource.com canonical name = deb.nodesource.com.cdn.cloudflare.net.
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 172.67.10.205
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.4.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.5.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::ac43:acd
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:41a
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:51a

12

You have something very odd going on, as that is a different ip.

What about dig deb.nodesource.com

13

And try rebooting the pi and the router.

14

I agree it quite odd....
I rebooted both router and Pi4. here's the output from dig on the pi4:
dig deb.nodesource.com

; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> deb.nodesource.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3117
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;deb.nodesource.com. IN A

;; ANSWER SECTION:
deb.nodesource.com. 216 IN CNAME deb.nodesource.com.cdn.cloudflare.net.
deb.nodesource.com.cdn.cloudflare.net. 216 IN A 104.22.4.26
deb.nodesource.com.cdn.cloudflare.net. 216 IN A 104.22.5.26
deb.nodesource.com.cdn.cloudflare.net. 216 IN A 172.67.10.205

;; Query time: 20 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Dec 11 12:39:13 EST 2023
;; MSG SIZE rcvd: 146

after the reboot, the install script still fails with the 503 error

15

See what this says

curl https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease|more

Edit:

Actually this might be more useful
wget https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease

16

wget https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
--2023-12-11 16:39:51-- https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
Resolving deb.nodesource.com (deb.nodesource.com)... 143.204.15.127
Connecting to deb.nodesource.com (deb.nodesource.com)|143.204.15.127|:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2023-12-11 16:39:52 ERROR 503: Service Unavailable.

looks like it goes to the wring URL...

17

Yes, that is the problem. You have something very wrong with your DNS.
What is in /etc/dhcpcd.conf? Watch the spelling, it is not dhcpd.conf or anything else similar.

18

I had set a static IP for this host in the past using /etc/dhcpd.conf. I eliminated these few lines from the file to allow the router to set the IP. After rebooting both the router and Pi 4 host. I checked the IP; it has changed to a new LAN IP, like you'd expect. Internet connectivity seems fine. However I still get the wrong IP when trying to connect to deb.nodesource.com:
wget https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
--2023-12-11 17:59:26-- https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
Resolving deb.nodesource.com (deb.nodesource.com)... 143.204.15.127
Connecting to deb.nodesource.com (deb.nodesource.com)|143.204.15.127|:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2023-12-11 17:59:27 ERROR 503: Service Unavailable.

pi@pihome:~ $ nslookup deb.nodesource.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
deb.nodesource.com canonical name = deb.nodesource.com.cdn.cloudflare.net.
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 172.67.10.205
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.5.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.4.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:41a
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:51a
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::ac43:acd

19

That's the same as on my Raspberry Pi running PiHole

pi@GlassPi:~ $ nslookup deb.nodesource.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
deb.nodesource.com canonical name = deb.nodesource.com.cdn.cloudflare.net.
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.5.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 172.67.10.205
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 104.22.4.26
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:51a
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::ac43:acd
Name: deb.nodesource.com.cdn.cloudflare.net
Address: 2606:4700:10::6816:41a

But wget works

wget https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
--2023-12-11 23:31:13--  https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
Resolving deb.nodesource.com (deb.nodesource.com)... 172.67.10.205, 104.22.5.26, 104.22.4.26, ...
Connecting to deb.nodesource.com (deb.nodesource.com)|172.67.10.205|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12140 (12K) [binary/octet-stream]
Saving to: ‘InRelease.1’

InRelease.1                                    100%[==================================================================================================>]  11.86K  --.-KB/s    in 0.001s

2023-12-11 23:31:13 (15.8 MB/s) - ‘InRelease.1’ saved [12140/12140]

So I don't think it's a DNS error?

20

Pihole is disabled on my Pi4.
the wget commnd you show here resolves to the correct IP address for deb.nodesource.com, but my system does not. Note the output form my wget resolves to a different IP; hence the 503 error:
wget -v https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
--2023-12-11 19:25:52-- https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease
Resolving deb.nodesource.com (deb.nodesource.com)... 143.204.15.127
Connecting to deb.nodesource.com (deb.nodesource.com)|143.204.15.127|:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2023-12-11 19:25:53 ERROR 503: Service Unavailable.

I haven't yet figured out why this happens.

21

Yes, I see that the DNS server reported by your dig command is 208.67.222.222 while nslookup uses localhost.

Does it make a difference if you specify DNS servers in your router - 1.1.1.1 or 8.8.8.8?