Can't get a cert on Synology NAS

Help
21

No IPv6 as in: FIOS has no IPv6 support, so it cannot possibly work. I was terse, sorry. I get that way after working for 36 hours.

22

COVID is also a factor - no worries

23

Please show the output of:
ifconfig

24

Hi @wwolf

I'm not firm with Synology. But sometimes the error messages are curious - "can't connect instead of can't create ...".

Is there an update? If yes, install it.

25

Same as before even after the reboottal. God I hate this Synology. And myself to know nothing.

Let me check if the off is really off… In the meantime:

root@wolfden:~# ifconfig | grep inet6
          inet6 addr: fe80::42:62ff:fe5c:a751/64 Scope:Link
          inet6 addr: fe80::7c50:48ff:feec:b432/64 Scope:Link
          inet6 addr: fe80::7028:9eff:fe18:94a8/64 Scope:Link
          inet6 addr: fe80::8880:dff:fe6d:3c78/64 Scope:Link
          inet6 addr: ::1/128 Scope:Host
26

not that output
without the grep
just
ifconfig

27

Do you want eth0 or all the docker madness as well?

28

Synology in docker?

Are you sure you are on the correct system?

Or maybe those are dockers/lets in Synology…?
[Not too familiar with their O/S setup]

29

No. Docker on Synology. Running docker instances show up as whatever fake devices.

30

Try it just on eth0 and eth1 (if that exists) then.

31

Tried something that says “Set as default gateway” for the IPv4 settings, but I get the same error. IPv6 is off in the control panel thing,.

root@wolfden:~# ifconfig
docker0   Link encap:Ethernet  HWaddr 02:42:62:5C:A7:51
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          inet6 addr: fe80::42:62ff:fe5c:a751/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1001 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:31149 (30.4 KiB)  TX bytes:2646129 (2.5 MiB)

docker070 Link encap:Ethernet  HWaddr 7E:50:48:EC:B4:32
          inet6 addr: fe80::7c50:48ff:feec:b432/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)

dockera3d Link encap:Ethernet  HWaddr 72:28:9E:18:94:A8
          inet6 addr: fe80::7028:9eff:fe18:94a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:538 (538.0 B)

dockercca Link encap:Ethernet  HWaddr 8A:80:0D:6D:3C:78
          inet6 addr: fe80::8880:dff:fe6d:3c78/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:38639 (37.7 KiB)  TX bytes:2646597 (2.5 MiB)

eth0      Link encap:Ethernet  HWaddr 00:11:32:5E:45:65
          inet addr:192.168.1.160  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11595 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16919 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4760198 (4.5 MiB)  TX bytes:18506833 (17.6 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2443 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2443 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:316156 (308.7 KiB)  TX bytes:316156 (308.7 KiB)
32

Hm. No inet6 for eth0.

33

It may be an “order matters” issue now.
In that, services seem to have been provisioned via IPv6.
So it might not let you remove/disable IPv6.

But we are still not 100% sure that IPv6 is the problem.
That was just my best hunch.

Are there any LE logs?

Check in file:
/var/log/messages

34

I don’t know about the logs. Where would they be if they were there? I mean I am using a web access thing called DSM, and that gives me the error message. Practically a GUI. I am not sure what it does.

35

Check in file:
/var/log/messages

36

Will do. Restarting it again.

1 Like
37

This is huge. Is there some phrase I should look for?

38

Let’s start with:
grep -i letsencrypt /var/log/messages

[to be sure there is even anything related in there]

OR you can move the current messages log file and rerun the cert get option.
All the would then be in the messages file should then be related to that last command issued.

39

I rerun it, I see this:

2020-08-10T03:26:39-04:00 wolfden syno-letsencrypt: syno-letsencrypt.cpp:121 Failed to do new authorization, may retry with another type. [{"error":200,"file":"client_v2.cpp","msg":"do new auth by path: failed to do challenge."}
]
2020-08-10T03:26:39-04:00 wolfden synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[21332]: certificate.cpp:965 syno-letsencrypt failed. 102 [Failed to new certificate.]
2020-08-10T03:26:39-04:00 wolfden synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[21332]: certificate.cpp:1399 Failed to create Let's Encrypt certificate. [102][Failed to new certificate.]
40

OK, this is different. I tried some other names also that are off. Let me try again.