Network Error - could not connect to the API server

Describe the problem

On my App, I see a lot of network errors, where records are briefly shown, then disappear.
https://spookycigars.baserow.site - see tabs ‘My Humidor’ or ‘My Cigar Journal’.

Describe, step by step, how to reproduce the error or problem you are encountering.

Click tabs mentioned above

Provide screenshots or include share links showing:

How many rows in total do you have in your Baserow tables?

about 1070 rows in total

Please attach full logs from all of Baserow’s services

??

Hi David,

We’ve been experiencing an issue today with a user making too many requests that had some knock on affects. We’ve taken action on the user so this won’t happen again.

Let me know if you have continued problems like this or if it has been resolved.

cwinhall,

Perhaps I should’ve been a bit more clear.

I’m experiencing this for a while now, for at least 2-3 weeks, not just today.

Hope this helps.
David

Hi @DavidCeulemans, thank you for reporting this problem. If it’s happening for 2-3 weeks already, then it shouldn’t be related to some peak usage from other users.

It would be great to learn more about when this problem is happening. Are there specific steps you can follow to reproduce these error messages? If so, can you share which steps those are, so that we can try to reproduce it.

If it happens randomly, I’m suspecting it might be a DNS problem. Do you have any experience with the command line? If so, it would be great if you can execute the following commands for me:

ping spookycigars.baserow.site
ping api.baserow.io
ping baserow.io

dig spookycigars.baserow.site
dig api.baserow.io
dig baserow.io

I’m curious about the output.

Hi Bram,

Ping results seem a bit random.

PING baserow.io (75.2.56.27): 56 data bytes
64 bytes from 75.2.56.27: icmp_seq=0 ttl=249 time=23.914 ms
64 bytes from 75.2.56.27: icmp_seq=1 ttl=249 time=23.481 ms
64 bytes from 75.2.56.27: icmp_seq=2 ttl=249 time=18.080 ms
64 bytes from 75.2.56.27: icmp_seq=3 ttl=249 time=26.025 ms
64 bytes from 75.2.56.27: icmp_seq=4 ttl=249 time=26.480 ms
64 bytes from 75.2.56.27: icmp_seq=5 ttl=249 time=18.674 ms
^Z
[1]+  Stopped                 ping spookycigars.baserow.site
Daves-MacBook-Pro:~ dave$ ping api.baserow.io
PING api.baserow.io (75.2.56.27): 56 data bytes
64 bytes from 75.2.56.27: icmp_seq=0 ttl=249 time=24.127 ms
64 bytes from 75.2.56.27: icmp_seq=1 ttl=249 time=22.741 ms
64 bytes from 75.2.56.27: icmp_seq=2 ttl=249 time=23.605 ms
64 bytes from 75.2.56.27: icmp_seq=3 ttl=249 time=31.653 ms
64 bytes from 75.2.56.27: icmp_seq=4 ttl=249 time=22.125 ms
^Z
[2]+  Stopped                 ping api.baserow.io
Daves-MacBook-Pro:~ dave$ ping baserow.io
PING baserow.io (75.2.56.27): 56 data bytes
64 bytes from 75.2.56.27: icmp_seq=0 ttl=249 time=28.253 ms
64 bytes from 75.2.56.27: icmp_seq=1 ttl=249 time=27.399 ms
64 bytes from 75.2.56.27: icmp_seq=2 ttl=249 time=23.601 ms
64 bytes from 75.2.56.27: icmp_seq=3 ttl=249 time=28.725 ms
64 bytes from 75.2.56.27: icmp_seq=4 ttl=249 time=20.373 ms
64 bytes from 75.2.56.27: icmp_seq=5 ttl=249 time=27.627 ms
^Z
[3]+  Stopped                 ping baserow.io
Daves-MacBook-Pro:~ dave$ ping spookycigars.baserow.site
PING baserow.io (18.156.86.62): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
^Z
[4]+  Stopped                 ping spookycigars.baserow.site
Daves-MacBook-Pro:~ dave$ ping api.baserow.io
PING api.baserow.io (75.2.56.27): 56 data bytes
64 bytes from 75.2.56.27: icmp_seq=0 ttl=249 time=19.534 ms
64 bytes from 75.2.56.27: icmp_seq=1 ttl=249 time=24.578 ms
64 bytes from 75.2.56.27: icmp_seq=2 ttl=249 time=21.938 ms
64 bytes from 75.2.56.27: icmp_seq=3 ttl=249 time=24.860 ms
64 bytes from 75.2.56.27: icmp_seq=4 ttl=249 time=28.208 ms
^Z
[5]+  Stopped                 ping api.baserow.io
Daves-MacBook-Pro:~ dave$ ping baserow.io
PING baserow.io (18.156.86.62): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^Z
[6]+  Stopped                 ping baserow.io
; <<>> DiG 9.10.6 <<>> spookycigars.baserow.site
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48094
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;spookycigars.baserow.site.	IN	A

;; ANSWER SECTION:
spookycigars.baserow.site. 60	IN	CNAME	baserow.io.
baserow.io.		33	IN	A	18.156.86.62
baserow.io.		33	IN	A	75.2.56.27
baserow.io.		33	IN	A	3.33.195.161

;; Query time: 203 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Jul 26 14:21:26 CEST 2024
;; MSG SIZE  rcvd: 126
 <<>> DiG 9.10.6 <<>> api.baserow.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41048
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.baserow.io.			IN	A

;; ANSWER SECTION:
api.baserow.io.		21	IN	A	18.156.86.62
api.baserow.io.		21	IN	A	75.2.56.27
api.baserow.io.		21	IN	A	3.33.195.161

;; Query time: 41 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Jul 26 14:22:08 CEST 2024
;; MSG SIZE  rcvd: 91
; <<>> DiG 9.10.6 <<>> baserow.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45310
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;baserow.io.			IN	A

;; ANSWER SECTION:
baserow.io.		42	IN	A	18.156.86.62
baserow.io.		42	IN	A	3.33.195.161
baserow.io.		42	IN	A	75.2.56.27

;; Query time: 48 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Jul 26 14:22:41 CEST 2024
;; MSG SIZE  rcvd: 87

Hi @DavidCeulemans, the results look good. Our services have multiple IP addresses where it can be reached on. The IP addresses I see in your ping and dig are correct. Would you mind monitoring the upcoming days if it still happens, and if so, try to figure if it’s a combination of steps that’s causing it?

hi Bram,

Didn’t get timed out pings lately, but the network error as described still happens frequently.
No steps to take, just load the page by clicking on the top buttons.

Less frequently, I get the error below:

hope this helps,
David