ValueError: Requesting

Help
1

Strange situation
log near

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[09:20:58] INFO: Selected http verification
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Connection refused
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

2

traceroute 172.65.32.248 and traceroute cloudflare.com
I kinda guess you misconfiged to route 172.X to somewhere else

4 Likes
3

log near

root@malina:/home/pi# traceroute 172.65.32.248
traceroute to 172.65.32.248 (172.65.32.248), 30 hops max, 60 byte packets
 1  newmail.pro (192.168.1.1)  0.567 ms  0.326 ms  0.431 ms
 2  10.4.240.1 (10.4.240.1)  1.882 ms  1.767 ms  1.815 ms
 3  81.200.9.245 (81.200.9.245)  1.996 ms  2.208 ms  2.100 ms
 4  cloudflare.msk.piter-ix.net (185.0.13.165)  3.263 ms  3.799 ms  3.696 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@malina:/home/pi#

root@malina:/home/pi# traceroute cloudflare.com
traceroute to cloudflare.com (104.16.133.229), 30 hops max, 60 byte packets
 1  newmail.pro (192.168.1.1)  1.869 ms  1.760 ms  1.679 ms
 2  10.4.240.1 (10.4.240.1)  6.230 ms  6.191 ms  6.122 ms
 3  81.200.9.245 (81.200.9.245)  3.433 ms  2.117 ms  2.008 ms
 4  cloudflare.msk.piter-ix.net (185.0.13.165)  3.549 ms  3.686 ms  3.578 ms
 5  104.16.133.229 (104.16.133.229)  2.580 ms  2.635 ms  2.532 ms
root@malina:/home/pi#
4

ip route?

4 Likes
5

Strange .
After restarting, the certificate was received.

Problem solved

1 Like
6

hmm...
Does rebooting it get another Internet IP address?

OR

Are you just one of the lucky ones that "when all else fails... just reboot" and that fixes everything! ?

3 Likes
7

No, I have a dedicated static address, for Mikrotik.
Apparently I'm lucky. I rebooted Mikrotik + Raspberry and everything worked. It’s very strange because I rebooted just for luck. There were no prerequisites for this

1 Like
8

Please show this again [maybe things did change]:

3 Likes
9

Strange behavior. Nothing changed. But it worked.

log near

root@malina:/home/pi# traceroute 172.65.32.248
traceroute to 172.65.32.248 (172.65.32.248), 30 hops max, 60 byte packets
 1  newmail.pro (192.168.1.1)  0.643 ms  0.383 ms  0.474 ms
 2  10.4.240.1 (10.4.240.1)  1.861 ms  1.746 ms  1.765 ms
 3  81.200.9.245 (81.200.9.245)  2.006 ms  2.108 ms  2.000 ms
 4  cloudflare.msk.piter-ix.net (185.0.13.165)  3.323 ms  3.596 ms  3.490 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@malina:/home/pi#
10

hmm...
That is strange.
Something did change... We just haven't been able to find it [yet].

What about?:
traceroute -T -p 443 172.65.32.248

4 Likes
11

If I understood the output correctly.
Everything is available, in principle there are no problems.
Where did she come from and where did she go. Unclear.

root@malina:/home/pi# traceroute -T -p 443 172.65.32.248
traceroute to 172.65.32.248 (172.65.32.248), 30 hops max, 60 byte packets
1 newmail.pro (192.168.1.1) 1.391 ms 1.318 ms 1.299 ms
2 10.4.240.1 (10.4.240.1) 8.048 ms 8.052 ms 8.019 ms
3 81.200.9.245 (81.200.9.245) 7.982 ms 8.018 ms 7.890 ms
4 cloudflare.msk.piter-ix.net (185.0.13.165) 4.132 ms 4.060 ms 4.520 ms
5 172.65.32.248 (172.65.32.248) 7.852 ms 7.726 ms 7.745 ms
root@malina:/home/pi#

2 Likes
12

OK.
So, it was always reaching CF.
I thought it was father than 5 hops - my bad

Then it was just something that cleared out with a reboot.
I'd make sure you have the latest code, and patches, in the Mikrotik router.

And I liked the "cotton eye joe" reference!

4 Likes
13

7.8 on board ...

I tried the last one, rolled back. It seemed like a crude version

14

If all else was working...
A reboot every 60 days [or so], is not a bad deal.

3 Likes
15

I reboot on schedule
05:55:00
1d 00:00:00

1 Like
16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.