container-test-run-certificates
checks.aarch64-linux.certificates
· build #729
· raw
1Machine state will be reset. To keep it, pass --keep-machine-state2start all VLans3(finished: start all VLans, in 0.00 seconds)45Test will time out and terminate in 3600.0 seconds6run the VM test script7additionally exposed symbols:8 ca, client, server,9 vlan1,10 start_all, test_script, machines, machines_qemu, machines_nspawn, vlans, driver, log, os, create_machine, subtest, run_tests, join_all, retry, serial_stdout_off, serial_stdout_on, polling_condition, BaseMachine, QemuMachine, NspawnMachine, t, debug, dump_machine_ssh11start all VMs12client: systemd-nspawn running (pid 54)13ca: systemd-nspawn running (pid 53)14server: systemd-nspawn running (pid 55)15client: Waiting for journal at /build/vm-state-client/var/log/journal...16server: Waiting for journal at /build/vm-state-server/var/log/journal...17ca: Waiting for journal at /build/vm-state-ca/var/log/journal...18(finished: start all VMs, in 0.00 seconds)19nixos-nspawn(server): TAP vde-tap1 not found; container will be isolated from VDE20nixos-nspawn(server): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.21nixos-nspawn(client): TAP vde-tap1 not found; container will be isolated from VDE22nixos-nspawn(client): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.23nixos-nspawn(ca): TAP vde-tap1 not found; container will be isolated from VDE24nixos-nspawn(ca): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.25Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.26Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.27Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.28░ Spawning container client on /build/vm-state-client.29░ Spawning container server on /build/vm-state-server.30░ Spawning container ca on /build/vm-state-ca.31client # No journal files were found.32client # No journal boot entry found for the specified boot (+0).33server # No journal files were found.34server # No journal boot entry found for the specified boot (+0).35ca # No journal files were found.36ca # No journal boot entry found for the specified boot (+0).37client # [1410612.627384] client systemd-journald[72]: Journal started38client # [1410612.627436] client systemd-journald[72]: Runtime Journal (/run/log/journal/9e565f42ff524723b22129baf50b5cf3) is 8M, max 2.5G, 2.4G free.39client # [1410612.634005] client systemd[1]: Finished Apply Kernel Variables.40client # [1410612.646260] client systemd[1]: Finished Create Static Device Nodes in /dev gracefully.41client # [1410612.660701] client systemd[1]: Starting Flush Journal to Persistent Storage...42client # [1410612.661695] client systemd[1]: Starting Network Name Resolution...43client # [1410612.662675] client systemd[1]: Starting Create Static Device Nodes in /dev...44client # [1410612.669978] client systemd-journald[72]: Time spent on flushing to /var/log/journal/9e565f42ff524723b22129baf50b5cf3 is 1.319ms for 7 entries.45client # [1410612.669978] client systemd-journald[72]: System Journal (/var/log/journal/9e565f42ff524723b22129baf50b5cf3) is 8M, max 4G, 3.9G free.46client # [1410612.694334] client systemd[1]: Finished Create Static Device Nodes in /dev.47client # [1410612.694988] client systemd[1]: Reached target Preparation for Local File Systems.48client # [1410612.695155] client systemd[1]: Reached target Local File Systems.49client # [1410612.695976] client systemd[1]: Listening on Boot Loader Control Service Socket.50client # [1410612.696041] client systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container51client # [1410612.696820] client systemd[1]: Starting Save Transient machine-id to Disk...52client # [1410612.696855] client systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys53client # [1410612.753318] client systemd[1]: Finished Flush Journal to Persistent Storage.54client # [1410612.754378] client systemd[1]: Starting Create System Files and Directories...55client # [1410612.796339] client systemd[1]: Finished Firewall.56client # [1410612.796593] client systemd[1]: Reached target Preparation for Network.57client # [1410612.796821] client systemd[1]: Listening on Network Management Resolve Hook Socket.58client # [1410612.797886] client systemd[1]: Starting Network Management...59client # [1410612.809653] client systemd-tmpfiles[157]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted60client # [1410612.809876] client systemd-tmpfiles[157]: fchmod() of /var/log/journal failed: Operation not permitted61client # [1410612.810037] client systemd-tmpfiles[157]: fchmod() of /var/log/journal/9e565f42ff524723b22129baf50b5cf3 failed: Operation not permitted62client # [1410612.810274] client systemd-tmpfiles[157]: fchmod() of /run/log/journal failed: Operation not permitted63client # [1410612.818407] client systemd[1]: Finished Create System Files and Directories.64client # [1410612.820578] client systemd[1]: Starting Rebuild Journal Catalog...65client # [1410612.821669] client systemd[1]: Starting Record System Boot/Shutdown in UTMP...66client # [1410612.837796] client systemd[1]: Finished Record System Boot/Shutdown in UTMP.67server # [1410612.617898] server systemd-journald[72]: Journal started68client # [1410612.845030] client systemd[1]: Finished Rebuild Journal Catalog.69server # [1410612.617955] server systemd-journald[72]: Runtime Journal (/run/log/journal/4e9b969740de49bd91681be7965fe6ac) is 8M, max 2.5G, 2.4G free.70client # [1410612.846593] client systemd[1]: Starting Update is Completed...71server # [1410612.624180] server systemd[1]: Finished Apply Kernel Variables.72client # [1410612.856992] client systemd[1]: Finished Update is Completed.73server # [1410612.636749] server systemd[1]: Finished Create Static Device Nodes in /dev gracefully.74client # [1410613.545870] client systemd-networkd[178]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted75server # [1410612.650887] server systemd[1]: Starting Flush Journal to Persistent Storage...76client # [1410613.545961] client systemd-networkd[178]: Failed to increase receive buffer size for nftables netlink socket, ignoring: Operation not permitted77server # [1410612.651755] server systemd[1]: Starting Network Name Resolution...78ca # [1410612.626959] ca systemd-journald[81]: Journal started79server # [1410612.652418] server systemd[1]: Starting Create Static Device Nodes in /dev...80ca # [1410612.627016] ca systemd-journald[81]: Runtime Journal (/run/log/journal/976266f4f8084d3aa5e588e70b8ed158) is 8M, max 2.5G, 2.4G free.81server # [1410612.662833] server systemd-journald[72]: Time spent on flushing to /var/log/journal/4e9b969740de49bd91681be7965fe6ac is 3.018ms for 7 entries.82ca # [1410612.633199] ca systemd[1]: Finished Apply Kernel Variables.83client # [1410613.555933] client systemd-networkd[178]: /etc/systemd/network/99-ethernet-default-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.84ca # [1410612.645432] ca systemd[1]: Finished Create Static Device Nodes in /dev gracefully.85client # [1410613.556123] client systemd-networkd[178]: /etc/systemd/network/99-wireless-client-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.86ca # [1410612.659873] ca systemd[1]: Starting Flush Journal to Persistent Storage...87client # [1410613.556274] client systemd-networkd[178]: lo: Link UP88ca # [1410612.660747] ca systemd[1]: Starting Network Name Resolution...89client # [1410613.556279] client systemd-networkd[178]: lo: Gained carrier90ca # [1410612.661367] ca systemd[1]: Starting Create Static Device Nodes in /dev...91client # [1410613.556449] client systemd-networkd[178]: eth1: Configuring with /etc/systemd/network/40-eth1.network.92ca # [1410612.670429] ca systemd-journald[81]: Time spent on flushing to /var/log/journal/976266f4f8084d3aa5e588e70b8ed158 is 2.566ms for 7 entries.93client # [1410613.556874] client systemd[1]: Started Network Management.94ca # [1410612.670429] ca systemd-journald[81]: System Journal (/var/log/journal/976266f4f8084d3aa5e588e70b8ed158) is 8M, max 4G, 3.9G free.95ca # [1410612.694194] ca systemd[1]: Finished Create Static Device Nodes in /dev.96ca # [1410612.694871] ca systemd[1]: Reached target Preparation for Local File Systems.97ca # [1410612.695002] ca systemd[1]: Reached target Local File Systems.98ca # [1410612.695918] ca systemd[1]: Listening on Boot Loader Control Service Socket.99ca # [1410612.695973] ca systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container100ca # [1410612.696819] ca systemd[1]: Starting Save Transient machine-id to Disk...101server # [1410612.662833] server systemd-journald[72]: System Journal (/var/log/journal/4e9b969740de49bd91681be7965fe6ac) is 8M, max 4G, 3.9G free.102ca # [1410612.696855] ca systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys103server # [1410612.670642] server systemd[1]: Finished Create Static Device Nodes in /dev.104ca # [1410612.753953] ca systemd[1]: Finished Flush Journal to Persistent Storage.105server # [1410612.671332] server systemd[1]: Reached target Preparation for Local File Systems.106ca # [1410612.755437] ca systemd[1]: Starting Create System Files and Directories...107server # [1410612.671459] server systemd[1]: Reached target Local File Systems.108ca # [1410612.796348] ca systemd[1]: Finished Firewall.109server # [1410612.672363] server systemd[1]: Listening on Boot Loader Control Service Socket.110ca # [1410612.796589] ca systemd[1]: Reached target Preparation for Network.111server # [1410612.672416] server systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container112ca # [1410612.796810] ca systemd[1]: Listening on Network Management Resolve Hook Socket.113server # [1410612.673443] server systemd[1]: Starting Save Transient machine-id to Disk...114ca # [1410612.797879] ca systemd[1]: Starting Network Management...115server # [1410612.673479] server systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys116ca # [1410612.811341] ca systemd-tmpfiles[169]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted117server # [1410612.753862] server systemd[1]: Finished Flush Journal to Persistent Storage.118ca # [1410612.811602] ca systemd-tmpfiles[169]: fchmod() of /var/log/journal failed: Operation not permitted119server # [1410612.755586] server systemd[1]: Starting Create System Files and Directories...120ca # [1410612.811781] ca systemd-tmpfiles[169]: fchmod() of /var/log/journal/976266f4f8084d3aa5e588e70b8ed158 failed: Operation not permitted121server # [1410612.796344] server systemd[1]: Finished Firewall.122ca # [1410612.812058] ca systemd-tmpfiles[169]: fchmod() of /run/log/journal failed: Operation not permitted123server # [1410612.796583] server systemd[1]: Reached target Preparation for Network.124ca # [1410612.821859] ca systemd[1]: Finished Create System Files and Directories.125server # [1410612.796829] server systemd[1]: Listening on Network Management Resolve Hook Socket.126ca # [1410612.823609] ca systemd[1]: Starting Rebuild Journal Catalog...127server # [1410612.797889] server systemd[1]: Starting Network Management...128ca # [1410612.824900] ca systemd[1]: Starting Record System Boot/Shutdown in UTMP...129server # [1410612.811021] server systemd-tmpfiles[161]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted130ca # [1410612.836909] ca systemd[1]: Finished Record System Boot/Shutdown in UTMP.131server # [1410612.811272] server systemd-tmpfiles[161]: fchmod() of /var/log/journal failed: Operation not permitted132ca # [1410612.847515] ca systemd[1]: Finished Rebuild Journal Catalog.133server # [1410612.811445] server systemd-tmpfiles[161]: fchmod() of /var/log/journal/4e9b969740de49bd91681be7965fe6ac failed: Operation not permitted134ca # [1410612.848786] ca systemd[1]: Starting Update is Completed...135server # [1410612.811698] server systemd-tmpfiles[161]: fchmod() of /run/log/journal failed: Operation not permitted136ca # [1410612.858802] ca systemd[1]: Finished Update is Completed.137server # [1410612.818494] server systemd[1]: Finished Create System Files and Directories.138ca # [1410613.551102] ca systemd-networkd[191]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted139server # [1410612.820848] server systemd[1]: Starting Rebuild Journal Catalog...140ca # [1410613.551193] ca systemd-networkd[191]: Failed to increase receive buffer size for nftables netlink socket, ignoring: Operation not permitted141server # [1410612.821981] server systemd[1]: Starting Record System Boot/Shutdown in UTMP...142ca # [1410613.561592] ca systemd-networkd[191]: /etc/systemd/network/99-ethernet-default-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.143server # [1410612.837390] server systemd[1]: Finished Record System Boot/Shutdown in UTMP.144ca # [1410613.561763] ca systemd-networkd[191]: /etc/systemd/network/99-wireless-client-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.145server # [1410612.846285] server systemd[1]: Finished Rebuild Journal Catalog.146ca # [1410613.561904] ca systemd-networkd[191]: lo: Link UP147server # [1410612.848075] server systemd[1]: Starting Update is Completed...148ca # [1410613.561908] ca systemd-networkd[191]: lo: Gained carrier149server # [1410612.859228] server systemd[1]: Finished Update is Completed.150ca # [1410613.562095] ca systemd-networkd[191]: eth1: Configuring with /etc/systemd/network/40-eth1.network.151server # [1410613.532116] server systemd-networkd[182]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted152ca # [1410613.562478] ca systemd[1]: Started Network Management.153server # [1410613.532208] server systemd-networkd[182]: Failed to increase receive buffer size for nftables netlink socket, ignoring: Operation not permitted154server # [1410613.543535] server systemd-networkd[182]: /etc/systemd/network/99-ethernet-default-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.155server # [1410613.543702] server systemd-networkd[182]: /etc/systemd/network/99-wireless-client-dhcp.network: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add Name=* in the [Match] section.156server # [1410613.543860] server systemd-networkd[182]: lo: Link UP157server # [1410613.543865] server systemd-networkd[182]: lo: Gained carrier158server # [1410613.544076] server systemd-networkd[182]: eth1: Configuring with /etc/systemd/network/40-eth1.network.159server # [1410613.544479] server systemd[1]: Started Network Management.160server # [1410613.544531] server systemd-networkd[182]: eth1: Link UP161server # [1410613.544844] server systemd-networkd[182]: eth1: Gained carrier162server # [1410613.546337] server systemd[1]: Starting Enable Persistent Storage in systemd-networkd...163ca # [1410613.596657] ca systemd-networkd[191]: eth1: Link UP164ca # [1410613.596693] ca systemd[1]: Starting Enable Persistent Storage in systemd-networkd...165ca # [1410613.597048] ca systemd-networkd[191]: eth1: Gained carrier166ca # [1410613.641310] ca systemd[1]: Finished Enable Persistent Storage in systemd-networkd.167server # [1410613.632366] server systemd[1]: Finished Enable Persistent Storage in systemd-networkd.168client # [1410613.596339] client systemd-networkd[178]: eth1: Link UP169client # [1410613.596526] client systemd[1]: Starting Enable Persistent Storage in systemd-networkd...170client # [1410613.596743] client systemd-networkd[178]: eth1: Gained carrier171client # [1410613.641626] client systemd[1]: Finished Enable Persistent Storage in systemd-networkd.172server # [1410613.903835] server systemd-resolved[104]: Positive Trust Anchors:173server # [1410613.903846] server systemd-resolved[104]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d174server # [1410613.903850] server systemd-resolved[104]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16175server # [1410613.903886] server systemd-resolved[104]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test176server # [1410613.926631] server systemd-resolved[104]: Using system hostname 'server'.177server # [1410613.927992] server systemd[1]: Started Network Name Resolution.178server # [1410613.928171] server systemd[1]: Reached target Network.179server # [1410613.928289] server systemd[1]: Reached target Network is Online.180server # [1410613.928384] server systemd[1]: Reached target System Initialization.181server # [1410613.928804] server systemd[1]: Started Renew ACME Certificate for test.foo.182server # [1410613.928865] server systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container183server # [1410613.928913] server systemd[1]: Started Daily Cleanup of Temporary Directories.184server # [1410613.928953] server systemd[1]: Reached target Timer Units.185server # [1410613.929203] server systemd[1]: Listening on D-Bus System Message Bus Socket.186server # [1410613.929422] server systemd[1]: Listening on Nix Daemon Socket.187server # [1410613.929644] server systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.188server # [1410613.929696] server systemd[1]: Reached target Socket Units.189server # [1410613.929775] server systemd[1]: Reached target Basic System.190server # [1410613.932113] server systemd[1]: Starting Set up the ACME certificate renewal infrastructure...191server # [1410613.933506] server systemd[1]: Starting Import lastlog data into lastlog2 database...192server # [1410613.933578] server systemd[1]: nginx-config-reload.service skipped, unmet condition check ConditionPathExists=/var/lib/acme/test.foo/fullchain.pem193server # [1410613.935060] server systemd[1]: Starting Name Service Cache Daemon (nsncd)...194server # [1410613.937358] server systemd[1]: Starting D-Bus System Message Bus...195server # [1410614.012666] server systemd[1]: Finished Import lastlog data into lastlog2 database.196server # [1410614.101681] server systemd[1]: etc-machine\x2did.mount: Deactivated successfully.197server # [1410614.103890] server systemd[1]: Finished Save Transient machine-id to Disk.198ca # [1410613.924489] ca systemd-resolved[115]: Positive Trust Anchors:199ca # [1410613.924499] ca systemd-resolved[115]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d200ca # [1410613.924501] ca systemd-resolved[115]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16201ca # [1410613.924535] ca systemd-resolved[115]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test202ca # [1410613.946108] ca systemd-resolved[115]: Using system hostname 'ca'.203ca # [1410613.947419] ca systemd[1]: Started Network Name Resolution.204ca # [1410613.947575] ca systemd[1]: Reached target Network.205ca # [1410613.947690] ca systemd[1]: Reached target Network is Online.206ca # [1410613.947788] ca systemd[1]: Reached target System Initialization.207ca # [1410613.948240] ca systemd[1]: Started Renew ACME Certificate for ca.foo.208ca # [1410613.948301] ca systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container209ca # [1410613.948349] ca systemd[1]: Started Daily Cleanup of Temporary Directories.210ca # [1410613.948397] ca systemd[1]: Reached target Timer Units.211ca # [1410613.948655] ca systemd[1]: Listening on D-Bus System Message Bus Socket.212ca # [1410613.950746] ca systemd[1]: Listening on Nix Daemon Socket.213ca # [1410613.950989] ca systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.214ca # [1410613.951041] ca systemd[1]: Reached target Socket Units.215ca # [1410613.951136] ca systemd[1]: Reached target Basic System.216ca # [1410613.992812] ca systemd[1]: Starting Set up the ACME certificate renewal infrastructure...217ca # [1410613.994913] ca systemd[1]: Starting Import lastlog data into lastlog2 database...218ca # [1410613.994988] ca systemd[1]: nginx-config-reload.service skipped, unmet condition check ConditionPathExists=/var/lib/acme/ca.foo/fullchain.pem219ca # [1410613.996768] ca systemd[1]: Starting Name Service Cache Daemon (nsncd)...220ca # [1410613.998818] ca systemd[1]: Starting step-ca service...221ca # [1410614.001378] ca systemd[1]: Starting D-Bus System Message Bus...222ca # [1410614.101628] ca systemd[1]: etc-machine\x2did.mount: Deactivated successfully.223ca # [1410614.136233] ca systemd[1]: Finished Save Transient machine-id to Disk.224ca # [1410614.136866] ca systemd[1]: Finished Import lastlog data into lastlog2 database.225ca # [1410614.216710] ca acme-setup-privileged[203]: + set -euo pipefail226ca # [1410614.216710] ca acme-setup-privileged[203]: + cd /var/lib/acme227ca # [1410614.216710] ca acme-setup-privileged[203]: + chmod -R u=rwX,g=,o= .lego/accounts228client # [1410613.915715] client systemd-resolved[105]: Positive Trust Anchors:229client # [1410613.915725] client systemd-resolved[105]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d230client # [1410613.915728] client systemd-resolved[105]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16231client # [1410613.915763] client systemd-resolved[105]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test232client # [1410613.937649] client systemd-resolved[105]: Using system hostname 'client'.233client # [1410613.938978] client systemd[1]: Started Network Name Resolution.234client # [1410613.939140] client systemd[1]: Reached target Network.235client # [1410613.939269] client systemd[1]: Reached target System Initialization.236client # [1410613.939376] client systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container237client # [1410613.939432] client systemd[1]: Started Daily Cleanup of Temporary Directories.238client # [1410613.939467] client systemd[1]: Reached target Timer Units.239client # [1410613.939703] client systemd[1]: Listening on D-Bus System Message Bus Socket.240client # [1410613.939959] client systemd[1]: Listening on Nix Daemon Socket.241client # [1410613.940228] client systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.242client # [1410613.940285] client systemd[1]: Reached target Socket Units.243client # [1410613.940376] client systemd[1]: Reached target Basic System.244client # [1410613.992653] client systemd[1]: Starting Import lastlog data into lastlog2 database...245client # [1410613.994585] client systemd[1]: Starting Name Service Cache Daemon (nsncd)...246client # [1410613.995996] client systemd[1]: Starting D-Bus System Message Bus...247client # [1410614.014810] client systemd[1]: Finished Import lastlog data into lastlog2 database.248client # [1410614.101584] client systemd[1]: etc-machine\x2did.mount: Deactivated successfully.249client # [1410614.103849] client systemd[1]: Finished Save Transient machine-id to Disk.250ca: must succeed: systemctl restart acme-order-renew-ca.foo.service 251ca # [1410614.218576] ca acme-setup-privileged[203]: + chown -R acme .lego/accounts252ca # [1410614.220370] ca acme-setup-privileged[203]: + for fixpath in ca.foo .lego/ca.foo253ca # [1410614.220370] ca acme-setup-privileged[203]: + '[' -d ca.foo ']'254ca # [1410614.220494] ca acme-setup-privileged[203]: + for fixpath in ca.foo .lego/ca.foo255ca # [1410614.220494] ca acme-setup-privileged[203]: + '[' -d .lego/ca.foo ']'256ca # [1410614.238052] ca nsncd[205]: Sep 20 15:17:14.223 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"257ca # [1410614.264699] ca systemd[1]: Started Name Service Cache Daemon (nsncd).258ca # [1410614.264920] ca systemd[1]: Reached target Host and Network Name Lookups.259ca # [1410614.265006] ca systemd[1]: Reached target User and Group Name Lookups.260ca # [1410614.266818] ca systemd[1]: Starting User Login Management...261ca # [1410614.268098] ca systemd[1]: Starting Permit User Sessions...262ca # [1410614.279436] ca systemd[1]: Finished Permit User Sessions.263ca # [1410614.280978] ca systemd[1]: Started Console Getty.264ca # [1410614.281032] ca systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0265ca # [1410614.281051] ca systemd[1]: Reached target Login Prompts.266ca # [1410614.454293] ca dbus-broker-launch[208]: Looking up NSS user entry for 'systemd-timesync'...267ca # [1410614.455780] ca dbus-broker-launch[208]: NSS returned no entry for 'systemd-timesync'268ca # [1410614.455780] ca dbus-broker-launch[208]: Invalid user-name in /nix/store/bh2gmvmbmbp0nqf3m5qaqnfjair6v85q-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"269ca # [1410614.456356] ca systemd[1]: Started D-Bus System Message Bus.270ca # [1410614.465119] ca dbus-broker-launch[208]: Ready271server # [1410614.208173] server acme-setup-privileged[194]: + set -euo pipefail272server # [1410614.208173] server acme-setup-privileged[194]: + cd /var/lib/acme273server # [1410614.208847] server acme-setup-privileged[194]: + chmod -R u=rwX,g=,o= .lego/accounts274server # [1410614.210582] server acme-setup-privileged[194]: + chown -R acme .lego/accounts275server # [1410614.213146] server acme-setup-privileged[194]: + for fixpath in test.foo .lego/test.foo276server # [1410614.213146] server acme-setup-privileged[194]: + '[' -d test.foo ']'277server # [1410614.213275] server acme-setup-privileged[194]: + for fixpath in test.foo .lego/test.foo278server # [1410614.213275] server acme-setup-privileged[194]: + '[' -d .lego/test.foo ']'279server # [1410614.299529] server nsncd[196]: Sep 20 15:17:14.285 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"280server # [1410614.299600] server systemd[1]: Started Name Service Cache Daemon (nsncd).281server # [1410614.299676] server systemd[1]: Reached target Host and Network Name Lookups.282server # [1410614.299745] server systemd[1]: Reached target User and Group Name Lookups.283server # [1410614.301300] server systemd[1]: Starting User Login Management...284server # [1410614.302241] server systemd[1]: Starting Permit User Sessions...285server # [1410614.312493] server systemd[1]: Finished Permit User Sessions.286server # [1410614.314905] server systemd[1]: Started Console Getty.287server # [1410614.314979] server systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0288server # [1410614.315023] server systemd[1]: Reached target Login Prompts.289server # [1410614.434461] server dbus-broker-launch[197]: Looking up NSS user entry for 'systemd-timesync'...290server # [1410614.435890] server dbus-broker-launch[197]: NSS returned no entry for 'systemd-timesync'291server # [1410614.435890] server dbus-broker-launch[197]: Invalid user-name in /nix/store/zzss1678mb50nlwag2hiw11lg128jpl3-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"292server # [1410614.436306] server systemd[1]: Started D-Bus System Message Bus.293server # [1410614.443966] server dbus-broker-launch[197]: Ready294client # [1410614.247555] client nsncd[191]: Sep 20 15:17:14.233 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"295client # [1410614.247536] client systemd[1]: Started Name Service Cache Daemon (nsncd).296client # [1410614.247659] client systemd[1]: Reached target Host and Network Name Lookups.297client # [1410614.247770] client systemd[1]: Reached target User and Group Name Lookups.298client # [1410614.265848] client systemd[1]: Starting User Login Management...299client # [1410614.267176] client systemd[1]: Starting Permit User Sessions...300client # [1410614.279121] client systemd[1]: Finished Permit User Sessions.301client # [1410614.280870] client systemd[1]: Started Console Getty.302client # [1410614.280953] client systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0303client # [1410614.280992] client systemd[1]: Reached target Login Prompts.304client # [1410614.440066] client dbus-broker-launch[192]: Looking up NSS user entry for 'systemd-timesync'...305client # [1410614.441493] client dbus-broker-launch[192]: NSS returned no entry for 'systemd-timesync'306client # [1410614.441493] client dbus-broker-launch[192]: Invalid user-name in /nix/store/g0a3fan1ykqwgcwicjzjgnwxr95dlfi7-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"307client # [1410614.441985] client systemd[1]: Started D-Bus System Message Bus.308client # [1410614.449799] client dbus-broker-launch[192]: Ready309server # [1410614.976086] server systemd-networkd[182]: eth1: Gained IPv6LL310server # [1410615.154273] server systemd-logind[227]: New seat seat0.311server # [1410615.154451] server systemd[1]: Started User Login Management.312server # [1410615.184855] server systemd[1]: Starting linger-users.service...313server # [1410615.198973] server systemd[1]: linger-users.service: Deactivated successfully.314server # [1410615.199117] server systemd[1]: Finished linger-users.service.315client # [1410615.139943] client systemd-logind[208]: New seat seat0.316client # [1410615.140170] client systemd[1]: Started User Login Management.317client # [1410615.142187] client systemd[1]: Starting linger-users.service...318client # [1410615.194030] client systemd[1]: linger-users.service: Deactivated successfully.319client # [1410615.194304] client systemd[1]: Finished linger-users.service.320client # [1410615.195181] client systemd[1]: Reached target Multi-User System.321client # [1410615.195500] client systemd[1]: Startup finished in 3.109s.322ca # [1410615.147430] ca systemd-logind[233]: New seat seat0.323ca # [1410615.147601] ca systemd[1]: Started User Login Management.324ca # [1410615.168134] ca systemd-networkd[191]: eth1: Gained IPv6LL325ca # [1410615.184674] ca systemd[1]: Starting linger-users.service...326ca # [1410615.198623] ca systemd[1]: linger-users.service: Deactivated successfully.327ca # [1410615.198713] ca systemd[1]: Finished linger-users.service.328ca # [1410615.281664] ca acme-setup-start[222]: + set -euo pipefail329ca # [1410615.281664] ca acme-setup-start[222]: + test -e ca/key.pem330ca # [1410615.282293] ca acme-setup-start[222]: + minica --ca-key ca/key.pem --ca-cert ca/cert.pem --domains selfsigned.local331ca # [1410615.320352] ca systemd[1]: Finished Set up the ACME certificate renewal infrastructure.332ca # [1410615.322315] ca systemd[1]: Starting Ensure certificate for ca.foo...333server # [1410615.246681] server acme-setup-start[211]: + set -euo pipefail334server # [1410615.246681] server acme-setup-start[211]: + test -e ca/key.pem335server # [1410615.246681] server acme-setup-start[211]: + minica --ca-key ca/key.pem --ca-cert ca/cert.pem --domains selfsigned.local336server # [1410615.270740] server systemd[1]: Finished Set up the ACME certificate renewal infrastructure.337server # [1410615.272845] server systemd[1]: Starting Ensure certificate for test.foo...338client # [1410615.392224] client systemd-networkd[178]: eth1: Gained IPv6LL339ca # [1410615.405142] ca step-ca[206]: badger 2026/09/20 15:17:15 INFO: All 0 tables opened in 0s340ca # [1410615.412114] ca step-ca[206]: 2026/09/20 15:17:15 Building new tls configuration using step-ca x509 Signer Interface341ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 Starting Smallstep CA/0.30.2 (linux/arm64)342ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 Documentation: https://u.step.sm/docs/ca343ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 Community Discord: https://u.step.sm/discord344ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 Config file: /etc/smallstep/ca.json345ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 The primary server URL is https://ca.foo:1443346ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 Root certificates are available at https://ca.foo:1443/roots.pem347ca # [1410615.418120] ca step-ca[206]: 2026/09/20 15:17:15 X.509 Root Fingerprint: 73a51e13ceeb202e4a617c48c0cd308f9567bdcba2ae26dbaab91234245a452e348ca # [1410615.418460] ca step-ca[206]: 2026/09/20 15:17:15 Serving HTTPS on 0.0.0.0:1443 ...349ca # [1410615.418540] ca systemd[1]: Started step-ca service.350ca # [1410616.224822] ca acme-ca.foo-start[263]: Waiting to acquire lock in /run/acme/351ca # [1410616.228337] ca acme-ca.foo-start[263]: + '[' -e out/acme-success ']'352ca # [1410616.228433] ca acme-ca.foo-start[263]: + minica --ca-cert=ca/cert.pem --ca-key=ca/key.pem --domains=ca.foo --ip-addresses=353ca # [1410616.243433] ca acme-ca.foo-start[296]: + cd ca.foo354ca # [1410616.243892] ca acme-ca.foo-start[296]: + cp -vp cert.pem ../out/cert.pem355ca # [1410616.245328] ca acme-ca.foo-start[297]: 'cert.pem' -> '../out/cert.pem'356ca # [1410616.245666] ca acme-ca.foo-start[296]: + cp -vp key.pem ../out/key.pem357ca # [1410616.246869] ca acme-ca.foo-start[296]: 'key.pem' -> '../out/key.pem'358ca # [1410616.247095] ca acme-ca.foo-start[263]: + cat out/cert.pem ca/cert.pem359ca # [1410616.248792] ca acme-ca.foo-start[263]: + cp ca/cert.pem out/chain.pem360ca # [1410616.250533] ca acme-ca.foo-start[263]: + cat out/key.pem out/fullchain.pem361ca # [1410616.252158] ca acme-ca.foo-start[263]: + for fixpath in out certificates362ca # [1410616.252158] ca acme-ca.foo-start[263]: + '[' -d out ']'363ca # [1410616.252267] ca acme-ca.foo-start[263]: + chmod -R u=rwX,g=rX,o= out364ca # [1410616.253791] ca acme-ca.foo-start[263]: + chown -R acme:nginx out365ca # [1410616.257134] ca acme-ca.foo-start[263]: + for fixpath in out certificates366ca # [1410616.257134] ca acme-ca.foo-start[263]: + '[' -d certificates ']'367ca # [1410616.262085] ca systemd[1]: Finished Ensure certificate for ca.foo.368ca # [1410616.264563] ca systemd[1]: Starting Nginx Web Server...369server # [1410616.237439] server acme-test.foo-start[247]: Waiting to acquire lock in /run/acme/370server # [1410616.240756] server acme-test.foo-start[247]: + '[' -e out/acme-success ']'371server # [1410616.240835] server acme-test.foo-start[247]: + minica --ca-cert=ca/cert.pem --ca-key=ca/key.pem --domains=test.foo --ip-addresses=372server # [1410616.255393] server acme-test.foo-start[257]: + cd test.foo373server # [1410616.255934] server acme-test.foo-start[257]: + cp -vp cert.pem ../out/cert.pem374server # [1410616.257369] server acme-test.foo-start[258]: 'cert.pem' -> '../out/cert.pem'375server # [1410616.257864] server acme-test.foo-start[257]: + cp -vp key.pem ../out/key.pem376server # [1410616.259053] server acme-test.foo-start[257]: 'key.pem' -> '../out/key.pem'377server # [1410616.259298] server acme-test.foo-start[247]: + cat out/cert.pem ca/cert.pem378server # [1410616.261324] server acme-test.foo-start[247]: + cp ca/cert.pem out/chain.pem379server # [1410616.262886] server acme-test.foo-start[247]: + cat out/key.pem out/fullchain.pem380server # [1410616.264730] server acme-test.foo-start[247]: + for fixpath in out certificates381server # [1410616.264730] server acme-test.foo-start[247]: + '[' -d out ']'382server # [1410616.264851] server acme-test.foo-start[247]: + chmod -R u=rwX,g=rX,o= out383server # [1410616.266383] server acme-test.foo-start[247]: + chown -R acme:nginx out384server # [1410616.270220] server acme-test.foo-start[247]: + for fixpath in out certificates385server # [1410616.270220] server acme-test.foo-start[247]: + '[' -d certificates ']'386server # [1410616.320250] server systemd[1]: Finished Ensure certificate for test.foo.387server # [1410616.322770] server systemd[1]: Starting Nginx Web Server...388ca # [1410617.259735] ca nginx-pre-start[308]: nginx: the configuration file /nix/store/9xdq48zsmbzh971fy8df0q5bz7cca117-nginx.conf syntax is ok389ca # [1410617.260339] ca nginx-pre-start[308]: nginx: configuration file /nix/store/9xdq48zsmbzh971fy8df0q5bz7cca117-nginx.conf test is successful390ca # [1410617.265274] ca systemd[1]: Started Nginx Web Server.391ca # [1410617.267043] ca systemd[1]: Reached target Multi-User System.392ca # [1410617.269357] ca systemd[1]: Starting Order (and renew) ACME certificate for ca.foo...393server # [1410617.228904] server nginx-pre-start[269]: nginx: the configuration file /nix/store/bw9jgq9jgvw8ia747pppjhkzskqcy6wl-nginx.conf syntax is ok394server # [1410617.229463] server nginx-pre-start[269]: nginx: configuration file /nix/store/bw9jgq9jgvw8ia747pppjhkzskqcy6wl-nginx.conf test is successful395server # [1410617.234468] server systemd[1]: Started Nginx Web Server.396server # [1410617.235910] server systemd[1]: Reached target Multi-User System.397server # [1410617.238266] server systemd[1]: Starting Order (and renew) ACME certificate for test.foo...398ca # [1410618.213006] ca acme-order-renew-ca.foo-start[311]: Waiting to acquire lock in /run/acme/399ca # [1410618.216259] ca acme-order-renew-ca.foo-start[311]: + set -euo pipefail400ca # [1410618.216335] ca acme-order-renew-ca.foo-start[311]: + exec401ca # [1410618.216380] ca acme-order-renew-ca.foo-start[311]: + /nix/store/fxkh6pl0y4nfbhdqdnhfkvsq7pbxq655-flock-0.4.0/bin/flock 11402ca # [1410618.218077] ca acme-order-renew-ca.foo-start[322]: ++ find accounts -path '*/keys/*.key' -print -quit403ca # [1410618.221227] ca acme-order-renew-ca.foo-start[311]: + '[' -n '' ']'404ca # [1410618.221269] ca acme-order-renew-ca.foo-start[311]: + exec405ca # [1410618.221341] ca acme-order-renew-ca.foo-start[311]: + '[' -e certificates/ca.foo.key ']'406ca # [1410618.221378] ca acme-order-renew-ca.foo-start[311]: + lego run --accept-tos --path . --email none@none.tld --http --http.webroot /var/lib/acme/acme-challenge --server https://ca.foo:1443/acme/acme/directory --key-type ec256 -d ca.foo --no-random-sleep --renew-force --ari-disable --force-cert-domains407ca # [1410618.241004] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.226793919Z INFO Private key saved. filepath=accounts/ca.foo_1443/none@none.tld/none@none.tld.key408ca # [1410618.284095] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration="181.442µs" duration-ns=181442 fields.time="2026-09-20T15:17:18Z" method=GET name=ca path=/acme/acme/directory protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=e258680d-83d1-4545-9108-a740d0ca9ea2 response="{\"newNonce\":\"https://ca.foo:1443/acme/acme/new-nonce\",\"newAccount\":\"https://ca.foo:1443/acme/acme/new-account\",\"newOrder\":\"https://ca.foo:1443/acme/acme/new-order\",\"revokeCert\":\"https://ca.foo:1443/acme/acme/revoke-cert\",\"keyChange\":\"https://ca.foo:1443/acme/acme/key-change\"}" size=277 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=409ca # [1410618.284865] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.270666558Z INFO Registering the account. email=none@none.tld410ca # [1410618.339969] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=54.678667ms duration-ns=54678667 fields.time="2026-09-20T15:17:18Z" method=HEAD name=ca nonce=M1I3ZXJzSVVuZ1lycHJhdDZucXRjSGN5TFVuQVFIOUY path=/acme/acme/new-nonce protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=ada1fb7b-cf70-4d3c-abc0-74b7da1742e0 size=0 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=411ca # [1410618.343849] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=3.071882ms duration-ns=3071882 fields.time="2026-09-20T15:17:18Z" method=POST name=ca nonce=dEJYOWpBaEg4UWEyZmFkdHRrUEVvRzJyZEVmMEo0cjc path=/acme/acme/new-account protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=8bb7aaed-25b3-4566-87eb-f2c9cd705212 response="{\"contact\":[\"mailto:none@none.tld\"],\"status\":\"valid\",\"orders\":\"https://ca.foo:1443/acme/acme/account/F8iNoxTadI4jHto1oPL6kjaoj6TW93Bw/orders\"}" size=143 status=201 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=412ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.330268453Z WARN !!!! HEADS UP !!!!413ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: Your account credentials have been saved in your414ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: configuration directory at "accounts".415ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: You should make a secure backup of this folder now. This416ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: configuration directory will also contain private keys417ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: generated by lego and certificates obtained from the ACME418ca # [1410618.344470] ca acme-order-renew-ca.foo-start[324]: server. Making regular backups of this folder is ideal.419ca # [1410618.344805] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.330514896Z INFO Obtaining bundled SAN certificate. domains=ca.foo420ca # [1410618.350004] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=4.40602ms duration-ns=4406020 fields.time="2026-09-20T15:17:18Z" method=POST name=ca nonce=enhoYjYxV3d3T2RsR2pyWDZwcFpQaThtbDJqYTh6UHE path=/acme/acme/new-order protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=faad63dd-9518-4bec-a6d3-ba782c307f74 response="{\"id\":\"Zw5pT7J5BKYXiwEAlp3eehvxGy4sTHUN\",\"status\":\"pending\",\"expires\":\"2026-09-21T15:17:18Z\",\"identifiers\":[{\"type\":\"dns\",\"value\":\"ca.foo\"}],\"notBefore\":\"2026-09-20T15:16:18Z\",\"notAfter\":\"2026-12-19T15:17:18Z\",\"authorizations\":[\"https://ca.foo:1443/acme/acme/authz/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe\"],\"finalize\":\"https://ca.foo:1443/acme/acme/order/Zw5pT7J5BKYXiwEAlp3eehvxGy4sTHUN/finalize\"}" size=392 status=201 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=421ca # [1410618.409564] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=2.076468ms duration-ns=2076468 fields.time="2026-09-20T15:17:18Z" method=POST name=ca nonce=VjFBZUVjN2pUUjA0bXE3VHBCbW5JbG5MSFNMeVNjSWs path=/acme/acme/authz/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=c1a3c158-5904-41d4-974e-67c8352fa6fd response="{\"identifier\":{\"type\":\"dns\",\"value\":\"ca.foo\"},\"status\":\"pending\",\"challenges\":[{\"type\":\"dns-01\",\"status\":\"pending\",\"token\":\"YSticmwpqovbOfZdjFHMpCIMbXyredLv\",\"url\":\"https://ca.foo:1443/acme/acme/challenge/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe/1KIh1WDhdK4o9dUWQf21gqx5CgIelmrC\"},{\"type\":\"http-01\",\"status\":\"pending\",\"token\":\"YSticmwpqovbOfZdjFHMpCIMbXyredLv\",\"url\":\"https://ca.foo:1443/acme/acme/challenge/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe/UPUvhPfrYGwNrJ1jRCQn8VgjU9MJ9TGm\"},{\"type\":\"tls-alpn-01\",\"status\":\"pending\",\"token\":\"YSticmwpqovbOfZdjFHMpCIMbXyredLv\",\"url\":\"https://ca.foo:1443/acme/acme/challenge/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe/lGRdIserY1nLGoMkmJT5gkshdEshieps\"}],\"wildcard\":false,\"expires\":\"2026-09-21T15:17:18Z\"}" size=719 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=422ca # [1410618.410048] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.395838429Z INFO Use solver. domain=ca.foo type=http-01423ca # [1410618.410137] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.395891229Z INFO http01: Trying to solve HTTP-01. domain=ca.foo424ca # [1410618.417889] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=6.948095ms duration-ns=6948095 fields.time="2026-09-20T15:17:18Z" method=POST name=ca nonce=MzZIeTNxcFU2VGw0YVlBdDBodTFyUkFvRUpneGtRZkg path=/acme/acme/challenge/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe/UPUvhPfrYGwNrJ1jRCQn8VgjU9MJ9TGm protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=eaf83f3c-4ec9-478a-85d9-963e783592ff response="{\"type\":\"http-01\",\"status\":\"valid\",\"token\":\"YSticmwpqovbOfZdjFHMpCIMbXyredLv\",\"validated\":\"2026-09-20T15:17:18Z\",\"url\":\"https://ca.foo:1443/acme/acme/challenge/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe/UPUvhPfrYGwNrJ1jRCQn8VgjU9MJ9TGm\"}" size=228 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=425ca # [1410618.418331] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.404121062Z INFO The server validated our request. domain=ca.foo426ca # [1410618.418469] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.404278384Z INFO Validations succeeded; requesting certificates. domains=ca.foo427ca # [1410618.429273] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info duration=9.029804ms duration-ns=9029804 fields.time="2026-09-20T15:17:18Z" method=POST name=ca nonce=TTRmakVjSkpuNzdlaHp3T2d0Mm1yQzZIS3NBd0xpWE4 path=/acme/acme/order/Zw5pT7J5BKYXiwEAlp3eehvxGy4sTHUN/finalize protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=5aacb5d2-b4eb-4bc6-bf34-a024c9e517d5 response="{\"id\":\"Zw5pT7J5BKYXiwEAlp3eehvxGy4sTHUN\",\"status\":\"valid\",\"expires\":\"2026-09-21T15:17:18Z\",\"identifiers\":[{\"type\":\"dns\",\"value\":\"ca.foo\"}],\"notBefore\":\"2026-09-20T15:16:18Z\",\"notAfter\":\"2026-12-19T15:17:18Z\",\"authorizations\":[\"https://ca.foo:1443/acme/acme/authz/r0eM9DC5MuzlG08tiHCWA9DOGhz4rgHe\"],\"finalize\":\"https://ca.foo:1443/acme/acme/order/Zw5pT7J5BKYXiwEAlp3eehvxGy4sTHUN/finalize\",\"certificate\":\"https://ca.foo:1443/acme/acme/certificate/u6JlapFtAuCPDut3JwfDUXIZoDc5e7Se\"}" size=481 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=428ca # [1410618.432056] ca step-ca[206]: time="2026-09-20T15:17:18Z" level=info certificate="MIIB1DCCAXmgAwIBAgIQTAbMkW1BV8V0uekxkf7RMTAKBggqhkjOPQQDAjAfMR0wGwYDVQQDExRDbGFuIEludGVybWVkaWF0ZSBDQTAeFw0yNjA5MjAxNTE2MThaFw0yNjEyMTkxNTE3MThaMBExDzANBgNVBAMTBmNhLmZvbzBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABFC1tvrh60GlGSmj/kYRJmCdt8XCOO5EWrL9XQC4o8I0/0170ERNhfAuz5owkeuRBVH7qROLiPK4KSfcqEEitD6jgaQwgaEwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjAdBgNVHQ4EFgQUANUs0zOQRPdB5MvgNq2n7BJyZhEwHwYDVR0jBBgwFoAUPhekAYvHnzzxhUbb2jb7u9rz2wIwEQYDVR0RBAowCIIGY2EuZm9vMB0GDCsGAQQBgqRkxihAAQQNMAsCAQYEBGFjbWUEADAKBggqhkjOPQQDAgNJADBGAiEAmomF6pOCqMLYVc0IlAvaoi7djJHgzmIT+q5Fu3c6vQUCIQCTVaqt5i0guyg6rgNbLlMS/ScDllHJmwrfw0ti6ZeJVQ==" duration=1.828465ms duration-ns=1828465 fields.time="2026-09-20T15:17:18Z" issuer="Clan Intermediate CA" method=POST name=ca nonce=YjlQVnFIejRrWGtzNXlYTll4R01RVDFtZ1BTME9HUzk path=/acme/acme/certificate/u6JlapFtAuCPDut3JwfDUXIZoDc5e7Se protocol=HTTP/1.1 provisioner=acme public-key="ECDSA P-256" referer= remote-address="2001:db8:1::1" request-id=b7024986-ff13-44ff-84d6-b9e299141563 sans="map[dns:[ca.foo]]" serial=101056630594260385552661121607892128049 size=1344 status=200 subject=ca.foo user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id= valid-from="2026-09-20T15:16:18Z" valid-to="2026-12-19T15:17:18Z"429ca # [1410618.432327] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.418126933Z INFO Server responded with a certificate. domains=ca.foo430ca # [1410618.432422] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.418236295Z INFO Writing file. filepath=certificates/ca.foo.crt431ca # [1410618.432579] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.418389817Z INFO Writing file. filepath=certificates/ca.foo.issuer.crt432ca # [1410618.432641] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.418465418Z INFO Writing file. filepath=certificates/ca.foo.key433ca # [1410618.432793] ca acme-order-renew-ca.foo-start[324]: 2026-09-20T15:17:18.418604180Z INFO Writing file. filepath=certificates/ca.foo.json434ca # [1410618.438209] ca acme-order-renew-ca.foo-start[311]: + touch out/acme-success435ca # [1410618.440317] ca acme-order-renew-ca.foo-start[311]: + cmp -s certificates/ca.foo.crt out/fullchain.pem436ca # [1410618.441723] ca acme-order-renew-ca.foo-start[311]: + touch out/renewed437ca # [1410618.443572] ca acme-order-renew-ca.foo-start[311]: + echo Installing new certificate438ca # [1410618.443572] ca acme-order-renew-ca.foo-start[311]: Installing new certificate439ca # [1410618.443572] ca acme-order-renew-ca.foo-start[311]: + cp -vp certificates/ca.foo.crt out/fullchain.pem440ca # [1410618.445280] ca acme-order-renew-ca.foo-start[355]: 'certificates/ca.foo.crt' -> 'out/fullchain.pem'441ca # [1410618.445656] ca acme-order-renew-ca.foo-start[311]: + cp -vp certificates/ca.foo.key out/key.pem442ca # [1410618.447040] ca acme-order-renew-ca.foo-start[356]: 'certificates/ca.foo.key' -> 'out/key.pem'443ca # [1410618.447357] ca acme-order-renew-ca.foo-start[311]: + cp -vp certificates/ca.foo.issuer.crt out/chain.pem444ca # [1410618.448775] ca acme-order-renew-ca.foo-start[357]: 'certificates/ca.foo.issuer.crt' -> 'out/chain.pem'445ca # [1410618.449069] ca acme-order-renew-ca.foo-start[311]: + ln -sf fullchain.pem out/cert.pem446ca # [1410618.451080] ca acme-order-renew-ca.foo-start[311]: + cat out/key.pem out/fullchain.pem447ca # [1410618.453236] ca acme-order-renew-ca.foo-start[311]: + for fixpath in out certificates448ca # [1410618.453236] ca acme-order-renew-ca.foo-start[311]: + '[' -d out ']'449ca # [1410618.453331] ca acme-order-renew-ca.foo-start[311]: + chmod -R u=rwX,g=rX,o= out450ca # [1410618.454914] ca acme-order-renew-ca.foo-start[311]: + chown -R acme:nginx out451ca # [1410618.458262] ca acme-order-renew-ca.foo-start[311]: + for fixpath in out certificates452ca # [1410618.458262] ca acme-order-renew-ca.foo-start[311]: + '[' -d certificates ']'453ca # [1410618.458262] ca acme-order-renew-ca.foo-start[311]: + chmod -R u=rwX,g=rX,o= certificates454ca # [1410618.459969] ca acme-order-renew-ca.foo-start[311]: + chown -R acme:nginx certificates455ca # [1410618.462897] ca acme-order-renew-ca.foo-start[311]: + chmod -R u=rwX,g=,o= accounts/.456server # [1410618.200216] server acme-order-renew-test.foo-start[272]: Waiting to acquire lock in /run/acme/457server # [1410618.203828] server acme-order-renew-test.foo-start[272]: + set -euo pipefail458server # [1410618.203828] server acme-order-renew-test.foo-start[272]: + exec459server # [1410618.203984] server acme-order-renew-test.foo-start[272]: + /nix/store/fxkh6pl0y4nfbhdqdnhfkvsq7pbxq655-flock-0.4.0/bin/flock 11460server # [1410618.205697] server acme-order-renew-test.foo-start[284]: ++ find accounts -path '*/keys/*.key' -print -quit461server # [1410618.208752] server acme-order-renew-test.foo-start[272]: + '[' -n '' ']'462server # [1410618.208834] server acme-order-renew-test.foo-start[272]: + exec463server # [1410618.208887] server acme-order-renew-test.foo-start[272]: + '[' -e certificates/test.foo.key ']'464server # [1410618.208887] server acme-order-renew-test.foo-start[272]: + lego run --accept-tos --path . --email none@none.tld --http --http.webroot /var/lib/acme/acme-challenge --server https://ca.foo/acme/acme/directory --key-type ec256 -d test.foo --no-random-sleep --renew-force --ari-disable --force-cert-domains465server # [1410618.238288] server acme-order-renew-test.foo-start[285]: 2026-09-20T15:17:18.224073361Z INFO Private key saved. filepath=accounts/ca.foo/none@none.tld/none@none.tld.key466server # [1410618.279713] server acme-order-renew-test.foo-start[285]: 2026-09-20T15:17:18.265506048Z ERROR Error error="registration: set up client: new client: get directory at 'https://ca.foo/acme/acme/directory': unable to communicate with the API server: error: Get \"https://ca.foo/acme/acme/directory\": GET https://ca.foo/acme/acme/directory giving up after 1 attempt(s): Get \"https://ca.foo/acme/acme/directory\": tls: failed to verify certificate: x509: certificate signed by unknown authority"467server # [1410618.280273] server acme-order-renew-test.foo-start[272]: + echo Failed to fetch certificates. This may mean your DNS records are set up incorrectly. Self-signed certs are in place and dependant services will still start.468server # [1410618.280273] server acme-order-renew-test.foo-start[272]: Failed to fetch certificates. This may mean your DNS records are set up incorrectly. Self-signed certs are in place and dependant services will still start.469server # [1410618.280273] server acme-order-renew-test.foo-start[272]: + exit 10470server # [1410618.284770] server systemd[1]: acme-order-renew-test.foo.service: Main process exited, code=exited, status=10/n/a471server # [1410618.284939] server systemd[1]: acme-order-renew-test.foo.service: Failed with result 'exit-code'.472server # [1410618.285333] server systemd[1]: Failed to start Order (and renew) ACME certificate for test.foo.473server # [1410618.285794] server systemd[1]: Startup finished in 6.198s.474server # [1410618.285857] server systemd[1]: acme-order-renew-test.foo.service: Consumed 1.026s CPU time over 1.046s wall clock time.475ca # [1410618.818080] ca systemd[1]: Reloading Nginx Web Server...476ca # [1410618.824815] ca systemd[1]: acme-order-renew-ca.foo.service: Deactivated successfully.477ca # [1410618.825032] ca systemd[1]: Finished Order (and renew) ACME certificate for ca.foo.478ca # [1410618.825231] ca systemd[1]: acme-order-renew-ca.foo.service: Consumed 1.268s CPU time over 1.555s wall clock time.479ca # [1410619.757570] ca nginx[373]: nginx: the configuration file /nix/store/9xdq48zsmbzh971fy8df0q5bz7cca117-nginx.conf syntax is ok480ca # [1410619.758052] ca nginx[373]: nginx: configuration file /nix/store/9xdq48zsmbzh971fy8df0q5bz7cca117-nginx.conf test is successful481ca # [1410620.752706] ca systemd[1]: Reloaded Nginx Web Server.482ca # [1410620.753199] ca systemd[1]: Startup finished in 8.648s.483ca # [1410621.219050] ca systemd[1]: Starting Order (and renew) ACME certificate for ca.foo...484ca # [1410622.185228] ca acme-order-renew-ca.foo-start[388]: Waiting to acquire lock in /run/acme/485ca # [1410622.188222] ca acme-order-renew-ca.foo-start[388]: + set -euo pipefail486ca # [1410622.188299] ca acme-order-renew-ca.foo-start[388]: + exec487ca # [1410622.188350] ca acme-order-renew-ca.foo-start[388]: + /nix/store/fxkh6pl0y4nfbhdqdnhfkvsq7pbxq655-flock-0.4.0/bin/flock 11488ca # [1410622.189589] ca acme-order-renew-ca.foo-start[396]: ++ find accounts -path '*/keys/*.key' -print -quit489ca # [1410622.192499] ca acme-order-renew-ca.foo-start[388]: + '[' -n '' ']'490ca # [1410622.192568] ca acme-order-renew-ca.foo-start[388]: + exec491ca # [1410622.192618] ca acme-order-renew-ca.foo-start[388]: + '[' -e certificates/ca.foo.key ']'492ca # [1410622.192618] ca acme-order-renew-ca.foo-start[388]: + '[' -e certificates/ca.foo.crt ']'493ca # [1410622.193201] ca acme-order-renew-ca.foo-start[397]: ++ find accounts -name none@none.tld.key494ca # [1410622.196916] ca acme-order-renew-ca.foo-start[388]: + '[' -n accounts/ca.foo_1443/none@none.tld/none@none.tld.key ']'495ca # [1410622.197006] ca acme-order-renew-ca.foo-start[388]: + lego run --accept-tos --path . --email none@none.tld --http --http.webroot /var/lib/acme/acme-challenge --server https://ca.foo:1443/acme/acme/directory --key-type ec256 -d ca.foo --no-random-sleep --force-cert-domains496ca # [1410622.218095] ca acme-order-renew-ca.foo-start[398]: 2026-09-20T15:17:22.203882550Z INFO Renewing certificate cert-name=ca.foo497ca # [1410622.246773] ca step-ca[206]: time="2026-09-20T15:17:22Z" level=info duration="50.64µs" duration-ns=50640 fields.time="2026-09-20T15:17:22Z" method=GET name=ca path=/acme/acme/directory protocol=HTTP/1.1 referer= remote-address="2001:db8:1::1" request-id=2eb200eb-8d5c-4ee8-88c0-a036758b1dfb response="{\"newNonce\":\"https://ca.foo:1443/acme/acme/new-nonce\",\"newAccount\":\"https://ca.foo:1443/acme/acme/new-account\",\"newOrder\":\"https://ca.foo:1443/acme/acme/new-order\",\"revokeCert\":\"https://ca.foo:1443/acme/acme/revoke-cert\",\"keyChange\":\"https://ca.foo:1443/acme/acme/key-change\"}" size=277 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=498ca # [1410622.247408] ca acme-order-renew-ca.foo-start[398]: 2026-09-20T15:17:22.233112709Z WARN The server does not advertise a renewal info endpoint. cert-name=ca.foo error="renewalInfo[get/post]: server does not advertise a renewal info endpoint"499ca # [1410622.247408] ca acme-order-renew-ca.foo-start[398]: 2026-09-20T15:17:22.233192350Z INFO Skip renewal: The certificate expires at 2026-12-19T15:17:18Z, the renewal can be performed in 59d23h59m35s766823250ns. cert-name=ca.foo500ca # [1410622.247904] ca acme-order-renew-ca.foo-start[388]: + touch out/acme-success501ca # [1410622.249535] ca acme-order-renew-ca.foo-start[388]: + cmp -s certificates/ca.foo.crt out/fullchain.pem502ca # [1410622.250863] ca acme-order-renew-ca.foo-start[388]: + for fixpath in out certificates503ca # [1410622.250863] ca acme-order-renew-ca.foo-start[388]: + '[' -d out ']'504ca # [1410622.250953] ca acme-order-renew-ca.foo-start[388]: + chmod -R u=rwX,g=rX,o= out505ca # [1410622.252785] ca acme-order-renew-ca.foo-start[388]: + chown -R acme:nginx out506ca # [1410622.255754] ca acme-order-renew-ca.foo-start[388]: + for fixpath in out certificates507ca # [1410622.255806] ca acme-order-renew-ca.foo-start[388]: + '[' -d certificates ']'508ca # [1410622.255806] ca acme-order-renew-ca.foo-start[388]: + chmod -R u=rwX,g=rX,o= certificates509ca # [1410622.257501] ca acme-order-renew-ca.foo-start[388]: + chown -R acme:nginx certificates510ca # [1410622.260806] ca acme-order-renew-ca.foo-start[388]: + chmod -R u=rwX,g=,o= accounts/.511ca: (finished: must succeed: systemctl restart acme-order-renew-ca.foo.service , in 7.93 seconds)512ca # [1410622.462581] ca systemd[1]: acme-order-renew-ca.foo.service: Deactivated successfully.513ca # [1410622.462931] ca systemd[1]: Finished Order (and renew) ACME certificate for ca.foo.514ca # [1410622.463473] ca systemd[1]: acme-order-renew-ca.foo.service: Consumed 1.185s CPU time over 1.243s wall clock time.515server: must succeed: systemctl restart acme-test.foo.service516server # [1410625.506496] server systemd[1]: acme-test.foo.service: Deactivated successfully.517server # [1410625.506709] server systemd[1]: Stopped Ensure certificate for test.foo.518server # [1410625.507645] server systemd[1]: Stopping Ensure certificate for test.foo...519server # [1410625.510364] server systemd[1]: Starting Ensure certificate for test.foo...520server: (finished: must succeed: systemctl restart acme-test.foo.service, in 0.97 seconds)521client: waiting for success: curl -v https://test.foo522* Host test.foo:443 was resolved.523* IPv6: 2001:db8:1::3524* IPv4: 192.168.1.3525* Trying [2001:db8:1::3]:443...526* ALPN: curl offers h2,http/1.1527} [5 bytes data]528* TLSv1.3 (OUT), TLS handshake, Client hello (1):529} [1552 bytes data]530* SSL Trust Anchors:531* OpenSSL default paths (fallback)532{ [5 bytes data]533* TLSv1.3 (IN), TLS handshake, Server hello (2):534{ [1210 bytes data]535* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):536{ [1 bytes data]537* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):538{ [19 bytes data]539* TLSv1.3 (IN), TLS handshake, Certificate (11):540{ [1010 bytes data]541* TLSv1.3 (IN), TLS handshake, CERT verify (15):542{ [112 bytes data]543* TLSv1.3 (IN), TLS handshake, Finished (20):544{ [52 bytes data]545* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):546} [1 bytes data]547* TLSv1.3 (OUT), TLS handshake, Finished (20):548} [52 bytes data]549* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey550* ALPN: server accepted h2551* Server certificate:552* subject: CN=test.foo553* start date: Sep 20 15:17:16 2026 GMT554* expire date: Oct 20 15:17:16 2028 GMT555* issuer: CN=minica root ca 10ef58556* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384557* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384558* subjectAltName: "test.foo" matches cert's "test.foo"559* OpenSSL verify result: 13560* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)561* closing connection #0562curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)563More details here: https://curl.se/docs/sslcerts.html564565curl failed to verify the legitimacy of the server and therefore could not566establish a secure connection to it. To learn more about this situation and567how to fix it, please visit the webpage mentioned above.568server # [1410626.422123] server acme-test.foo-start[318]: Waiting to acquire lock in /run/acme/569server # [1410626.425673] server acme-test.foo-start[318]: + '[' -e out/acme-success ']'570server # [1410626.425673] server acme-test.foo-start[318]: + minica --ca-cert=ca/cert.pem --ca-key=ca/key.pem --domains=test.foo --ip-addresses=571server # [1410626.441399] server acme-test.foo-start[327]: + cd test.foo572server # [1410626.441938] server acme-test.foo-start[327]: + cp -vp cert.pem ../out/cert.pem573server # [1410626.443360] server acme-test.foo-start[328]: 'cert.pem' -> '../out/cert.pem'574server # [1410626.443680] server acme-test.foo-start[327]: + cp -vp key.pem ../out/key.pem575server # [1410626.445102] server acme-test.foo-start[327]: 'key.pem' -> '../out/key.pem'576server # [1410626.445360] server acme-test.foo-start[318]: + cat out/cert.pem ca/cert.pem577server # [1410626.447339] server acme-test.foo-start[318]: + cp ca/cert.pem out/chain.pem578server # [1410626.448977] server acme-test.foo-start[318]: + cat out/key.pem out/fullchain.pem579server # [1410626.450604] server acme-test.foo-start[318]: + for fixpath in out certificates580server # [1410626.450604] server acme-test.foo-start[318]: + '[' -d out ']'581server # [1410626.450695] server acme-test.foo-start[318]: + chmod -R u=rwX,g=rX,o= out582server # [1410626.452447] server acme-test.foo-start[318]: + chown -R acme:nginx out583server # [1410626.455816] server acme-test.foo-start[318]: + for fixpath in out certificates584server # [1410626.455816] server acme-test.foo-start[318]: + '[' -d certificates ']'585server # [1410626.463769] server systemd[1]: Finished Ensure certificate for test.foo.586server # [1410626.468590] server systemd[1]: Starting Order (and renew) ACME certificate for test.foo...587* Host test.foo:443 was resolved.588* IPv6: 2001:db8:1::3589* IPv4: 192.168.1.3590* Trying [2001:db8:1::3]:443...591* ALPN: curl offers h2,http/1.1592} [5 bytes data]593* TLSv1.3 (OUT), TLS handshake, Client hello (1):594} [1552 bytes data]595* SSL Trust Anchors:596* OpenSSL default paths (fallback)597{ [5 bytes data]598* TLSv1.3 (IN), TLS handshake, Server hello (2):599{ [1210 bytes data]600* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):601{ [1 bytes data]602* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):603{ [19 bytes data]604* TLSv1.3 (IN), TLS handshake, Certificate (11):605{ [1010 bytes data]606* TLSv1.3 (IN), TLS handshake, CERT verify (15):607{ [112 bytes data]608* TLSv1.3 (IN), TLS handshake, Finished (20):609{ [52 bytes data]610* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):611} [1 bytes data]612* TLSv1.3 (OUT), TLS handshake, Finished (20):613} [52 bytes data]614* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey615* ALPN: server accepted h2616* Server certificate:617* subject: CN=test.foo618* start date: Sep 20 15:17:16 2026 GMT619* expire date: Oct 20 15:17:16 2028 GMT620* issuer: CN=minica root ca 10ef58621* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384622* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384623* subjectAltName: "test.foo" matches cert's "test.foo"624* OpenSSL verify result: 13625* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)626* closing connection #0627curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)628More details here: https://curl.se/docs/sslcerts.html629630curl failed to verify the legitimacy of the server and therefore could not631establish a secure connection to it. To learn more about this situation and632how to fix it, please visit the webpage mentioned above.633server # [1410627.430103] server acme-order-renew-test.foo-start[335]: Waiting to acquire lock in /run/acme/634server # [1410627.433587] server acme-order-renew-test.foo-start[335]: + set -euo pipefail635server # [1410627.433670] server acme-order-renew-test.foo-start[335]: + exec636server # [1410627.433720] server acme-order-renew-test.foo-start[335]: + /nix/store/fxkh6pl0y4nfbhdqdnhfkvsq7pbxq655-flock-0.4.0/bin/flock 11637server # [1410627.435353] server acme-order-renew-test.foo-start[343]: ++ find accounts -path '*/keys/*.key' -print -quit638server # [1410627.438410] server acme-order-renew-test.foo-start[335]: + '[' -n '' ']'639server # [1410627.438476] server acme-order-renew-test.foo-start[335]: + exec640server # [1410627.438526] server acme-order-renew-test.foo-start[335]: + '[' -e certificates/test.foo.key ']'641server # [1410627.438574] server acme-order-renew-test.foo-start[335]: + lego run --accept-tos --path . --email none@none.tld --http --http.webroot /var/lib/acme/acme-challenge --server https://ca.foo/acme/acme/directory --key-type ec256 -d test.foo --no-random-sleep --renew-force --ari-disable --force-cert-domains642server # [1410627.490665] server acme-order-renew-test.foo-start[344]: 2026-09-20T15:17:27.476433965Z INFO Trying to resolve the account by key643server # [1410627.499613] server acme-order-renew-test.foo-start[344]: 2026-09-20T15:17:27.485418648Z WARN retry: acme: error: 0 :: urn:ietf:params:acme:error:accountDoesNotExist :: Account does not exist644server # [1410627.499875] server acme-order-renew-test.foo-start[344]: 2026-09-20T15:17:27.485674331Z ERROR Error error="registration: resolve account by key: unable to communicate with the API server: error: Post \"https://ca.foo/acme/acme/new-account\": POST https://ca.foo/acme/acme/new-account giving up after 1 attempt(s): acme: error: 0 :: urn:ietf:params:acme:error:accountDoesNotExist :: Account does not exist"645server # [1410627.500366] server acme-order-renew-test.foo-start[335]: + echo Failed to fetch certificates. This may mean your DNS records are set up incorrectly. Self-signed certs are in place and dependant services will still start.646server # [1410627.500366] server acme-order-renew-test.foo-start[335]: Failed to fetch certificates. This may mean your DNS records are set up incorrectly. Self-signed certs are in place and dependant services will still start.647server # [1410627.500366] server acme-order-renew-test.foo-start[335]: + exit 10648server # [1410627.505244] server systemd[1]: acme-order-renew-test.foo.service: Main process exited, code=exited, status=10/n/a649server # [1410627.505447] server systemd[1]: acme-order-renew-test.foo.service: Failed with result 'exit-code'.650server # [1410627.505845] server systemd[1]: Failed to start Order (and renew) ACME certificate for test.foo.651ca # [1410627.489939] ca step-ca[206]: time="2026-09-20T15:17:27Z" level=info duration="51.841µs" duration-ns=51841 fields.time="2026-09-20T15:17:27Z" method=GET name=ca path=/acme/acme/directory protocol=HTTP/1.1 referer= remote-address="::1" request-id=5a2e95a7-516c-4818-9faa-8c3cac8fa22e response="{\"newNonce\":\"https://ca.foo/acme/acme/new-nonce\",\"newAccount\":\"https://ca.foo/acme/acme/new-account\",\"newOrder\":\"https://ca.foo/acme/acme/new-order\",\"revokeCert\":\"https://ca.foo/acme/acme/revoke-cert\",\"keyChange\":\"https://ca.foo/acme/acme/key-change\"}" size=252 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=652ca # [1410627.494699] ca step-ca[206]: time="2026-09-20T15:17:27Z" level=info duration="864.292µs" duration-ns=864292 fields.time="2026-09-20T15:17:27Z" method=HEAD name=ca nonce=RWpISkhFZVJoVE12ZGFMV1kzcHo2aEJvY1ZwclNReVU path=/acme/acme/new-nonce protocol=HTTP/1.1 referer= remote-address=127.0.0.1 request-id=5dcc76cf-7918-4fda-bcb1-3de7d2e88b0c size=0 status=200 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=653ca # [1410627.499136] ca step-ca[206]: time="2026-09-20T15:17:27Z" level=warning duration=1.47206ms duration-ns=1472060 error="account does not exist" fields.time="2026-09-20T15:17:27Z" method=POST name=ca nonce=a3VPMEx1eElQaHdmYkt4dFRKTm8zM001SDVOSUZhY3k path=/acme/acme/new-account protocol=HTTP/1.1 referer= remote-address="::1" request-id=c6679030-2526-4fc7-9d7a-693957ffc4af response="{\"type\":\"urn:ietf:params:acme:error:accountDoesNotExist\",\"detail\":\"Account does not exist\"}" size=92 status=400 user-agent="lego-cli/ xenolf-acme/5.4.1 (release; linux; arm64)" user-id=654* Host test.foo:443 was resolved.655* IPv6: 2001:db8:1::3656* IPv4: 192.168.1.3657* Trying [2001:db8:1::3]:443...658* ALPN: curl offers h2,http/1.1659} [5 bytes data]660* TLSv1.3 (OUT), TLS handshake, Client hello (1):661} [1552 bytes data]662* SSL Trust Anchors:663* OpenSSL default paths (fallback)664{ [5 bytes data]665* TLSv1.3 (IN), TLS handshake, Server hello (2):666{ [1210 bytes data]667* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):668{ [1 bytes data]669* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):670{ [19 bytes data]671* TLSv1.3 (IN), TLS handshake, Certificate (11):672{ [1010 bytes data]673* TLSv1.3 (IN), TLS handshake, CERT verify (15):674{ [110 bytes data]675* TLSv1.3 (IN), TLS handshake, Finished (20):676{ [52 bytes data]677* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):678} [1 bytes data]679* TLSv1.3 (OUT), TLS handshake, Finished (20):680} [52 bytes data]681* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey682* ALPN: server accepted h2683* Server certificate:684* subject: CN=test.foo685* start date: Sep 20 15:17:16 2026 GMT686* expire date: Oct 20 15:17:16 2028 GMT687* issuer: CN=minica root ca 10ef58688* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384689* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384690* subjectAltName: "test.foo" matches cert's "test.foo"691* OpenSSL verify result: 13692* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)693* closing connection #0694curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)695More details here: https://curl.se/docs/sslcerts.html696697curl failed to verify the legitimacy of the server and therefore could not698establish a secure connection to it. To learn more about this situation and699how to fix it, please visit the webpage mentioned above.700* Host test.foo:443 was resolved.701* IPv6: 2001:db8:1::3702* IPv4: 192.168.1.3703* Trying [2001:db8:1::3]:443...704* ALPN: curl offers h2,http/1.1705} [5 bytes data]706* TLSv1.3 (OUT), TLS handshake, Client hello (1):707} [1552 bytes data]708* SSL Trust Anchors:709* OpenSSL default paths (fallback)710{ [5 bytes data]711* TLSv1.3 (IN), TLS handshake, Server hello (2):712{ [1210 bytes data]713* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):714{ [1 bytes data]715* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):716{ [19 bytes data]717* TLSv1.3 (IN), TLS handshake, Certificate (11):718{ [1010 bytes data]719* TLSv1.3 (IN), TLS handshake, CERT verify (15):720{ [112 bytes data]721* TLSv1.3 (IN), TLS handshake, Finished (20):722{ [52 bytes data]723* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):724} [1 bytes data]725* TLSv1.3 (OUT), TLS handshake, Finished (20):726} [52 bytes data]727* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey728* ALPN: server accepted h2729* Server certificate:730* subject: CN=test.foo731* start date: Sep 20 15:17:16 2026 GMT732* expire date: Oct 20 15:17:16 2028 GMT733* issuer: CN=minica root ca 10ef58734* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384735* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384736* subjectAltName: "test.foo" matches cert's "test.foo"737* OpenSSL verify result: 13738* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)739* closing connection #0740curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)741More details here: https://curl.se/docs/sslcerts.html742743curl failed to verify the legitimacy of the server and therefore could not744establish a secure connection to it. To learn more about this situation and745how to fix it, please visit the webpage mentioned above.746* Trying [2001:db8:1::3]:443...747* Host test.foo:443 was resolved.748* IPv6: 2001:db8:1::3749* IPv4: 192.168.1.3750* ALPN: curl offers h2,http/1.1751} [5 bytes data]752* TLSv1.3 (OUT), TLS handshake, Client hello (1):753} [1552 bytes data]754* SSL Trust Anchors:755* OpenSSL default paths (fallback)756{ [5 bytes data]757* TLSv1.3 (IN), TLS handshake, Server hello (2):758{ [1210 bytes data]759* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):760{ [1 bytes data]761* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):762{ [19 bytes data]763* TLSv1.3 (IN), TLS handshake, Certificate (11):764{ [1010 bytes data]765* TLSv1.3 (IN), TLS handshake, CERT verify (15):766{ [110 bytes data]767* TLSv1.3 (IN), TLS handshake, Finished (20):768{ [52 bytes data]769* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):770} [1 bytes data]771* TLSv1.3 (OUT), TLS handshake, Finished (20):772} [52 bytes data]773* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey774* ALPN: server accepted h2775* Server certificate:776* subject: CN=test.foo777* start date: Sep 20 15:17:16 2026 GMT778* expire date: Oct 20 15:17:16 2028 GMT779* issuer: CN=minica root ca 10ef58780* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384781* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384782* subjectAltName: "test.foo" matches cert's "test.foo"783* OpenSSL verify result: 13784* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)785* closing connection #0786curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)787More details here: https://curl.se/docs/sslcerts.html788789curl failed to verify the legitimacy of the server and therefore could not790establish a secure connection to it. To learn more about this situation and791how to fix it, please visit the webpage mentioned above.792* Host test.foo:443 was resolved.793* IPv6: 2001:db8:1::3794* IPv4: 192.168.1.3795* Trying [2001:db8:1::3]:443...796* ALPN: curl offers h2,http/1.1797} [5 bytes data]798* TLSv1.3 (OUT), TLS handshake, Client hello (1):799} [1552 bytes data]800* SSL Trust Anchors:801* OpenSSL default paths (fallback)802{ [5 bytes data]803* TLSv1.3 (IN), TLS handshake, Server hello (2):804{ [1210 bytes data]805* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):806{ [1 bytes data]807* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):808{ [19 bytes data]809* TLSv1.3 (IN), TLS handshake, Certificate (11):810{ [1010 bytes data]811* TLSv1.3 (IN), TLS handshake, CERT verify (15):812{ [111 bytes data]813* TLSv1.3 (IN), TLS handshake, Finished (20):814{ [52 bytes data]815* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):816} [1 bytes data]817* TLSv1.3 (OUT), TLS handshake, Finished (20):818} [52 bytes data]819* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey820* ALPN: server accepted h2821* Server certificate:822* subject: CN=test.foo823* start date: Sep 20 15:17:16 2026 GMT824* expire date: Oct 20 15:17:16 2028 GMT825* issuer: CN=minica root ca 10ef58826* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384827* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384828* subjectAltName: "test.foo" matches cert's "test.foo"829* OpenSSL verify result: 13830* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)831* closing connection #0832curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)833More details here: https://curl.se/docs/sslcerts.html834835curl failed to verify the legitimacy of the server and therefore could not836establish a secure connection to it. To learn more about this situation and837how to fix it, please visit the webpage mentioned above.838* Host test.foo:443 was resolved.839* IPv6: 2001:db8:1::3840* IPv4: 192.168.1.3841* Trying [2001:db8:1::3]:443...842* ALPN: curl offers h2,http/1.1843} [5 bytes data]844* TLSv1.3 (OUT), TLS handshake, Client hello (1):845} [1552 bytes data]846* SSL Trust Anchors:847* OpenSSL default paths (fallback)848{ [5 bytes data]849* TLSv1.3 (IN), TLS handshake, Server hello (2):850{ [1210 bytes data]851* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):852{ [1 bytes data]853* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):854{ [19 bytes data]855* TLSv1.3 (IN), TLS handshake, Certificate (11):856{ [1010 bytes data]857* TLSv1.3 (IN), TLS handshake, CERT verify (15):858{ [112 bytes data]859* TLSv1.3 (IN), TLS handshake, Finished (20):860{ [52 bytes data]861* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):862} [1 bytes data]863* TLSv1.3 (OUT), TLS handshake, Finished (20):864} [52 bytes data]865* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey866* ALPN: server accepted h2867* Server certificate:868* subject: CN=test.foo869* start date: Sep 20 15:17:16 2026 GMT870* expire date: Oct 20 15:17:16 2028 GMT871* issuer: CN=minica root ca 10ef58872* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384873* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384874* subjectAltName: "test.foo" matches cert's "test.foo"875* OpenSSL verify result: 13876* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)877* closing connection #0878curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)879More details here: https://curl.se/docs/sslcerts.html880881curl failed to verify the legitimacy of the server and therefore could not882establish a secure connection to it. To learn more about this situation and883how to fix it, please visit the webpage mentioned above.884* Host test.foo:443 was resolved.885* IPv6: 2001:db8:1::3886* IPv4: 192.168.1.3887* Trying [2001:db8:1::3]:443...888* ALPN: curl offers h2,http/1.1889} [5 bytes data]890* TLSv1.3 (OUT), TLS handshake, Client hello (1):891} [1552 bytes data]892* SSL Trust Anchors:893* OpenSSL default paths (fallback)894{ [5 bytes data]895* TLSv1.3 (IN), TLS handshake, Server hello (2):896{ [1210 bytes data]897* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):898{ [1 bytes data]899* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):900{ [19 bytes data]901* TLSv1.3 (IN), TLS handshake, Certificate (11):902{ [1010 bytes data]903* TLSv1.3 (IN), TLS handshake, CERT verify (15):904{ [110 bytes data]905* TLSv1.3 (IN), TLS handshake, Finished (20):906{ [52 bytes data]907* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):908} [1 bytes data]909* TLSv1.3 (OUT), TLS handshake, Finished (20):910} [52 bytes data]911* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey912* ALPN: server accepted h2913* Server certificate:914* subject: CN=test.foo915* start date: Sep 20 15:17:16 2026 GMT916* expire date: Oct 20 15:17:16 2028 GMT917* issuer: CN=minica root ca 10ef58918* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384919* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384920* subjectAltName: "test.foo" matches cert's "test.foo"921* OpenSSL verify result: 13922* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)923* closing connection #0924curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)925More details here: https://curl.se/docs/sslcerts.html926927curl failed to verify the legitimacy of the server and therefore could not928establish a secure connection to it. To learn more about this situation and929how to fix it, please visit the webpage mentioned above.930* Host test.foo:443 was resolved.931* IPv6: 2001:db8:1::3932* IPv4: 192.168.1.3933* Trying [2001:db8:1::3]:443...934* ALPN: curl offers h2,http/1.1935} [5 bytes data]936* TLSv1.3 (OUT), TLS handshake, Client hello (1):937} [1552 bytes data]938* SSL Trust Anchors:939* OpenSSL default paths (fallback)940{ [5 bytes data]941* TLSv1.3 (IN), TLS handshake, Server hello (2):942{ [1210 bytes data]943* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):944{ [1 bytes data]945* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):946{ [19 bytes data]947* TLSv1.3 (IN), TLS handshake, Certificate (11):948{ [1010 bytes data]949* TLSv1.3 (IN), TLS handshake, CERT verify (15):950{ [112 bytes data]951* TLSv1.3 (IN), TLS handshake, Finished (20):952{ [52 bytes data]953* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):954} [1 bytes data]955* TLSv1.3 (OUT), TLS handshake, Finished (20):956} [52 bytes data]957* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey958* ALPN: server accepted h2959* Server certificate:960* subject: CN=test.foo961* start date: Sep 20 15:17:16 2026 GMT962* expire date: Oct 20 15:17:16 2028 GMT963* issuer: CN=minica root ca 10ef58964* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384965* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384966* subjectAltName: "test.foo" matches cert's "test.foo"967* OpenSSL verify result: 13968* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)969* closing connection #0970curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)971More details here: https://curl.se/docs/sslcerts.html972973curl failed to verify the legitimacy of the server and therefore could not974establish a secure connection to it. To learn more about this situation and975how to fix it, please visit the webpage mentioned above.976* Host test.foo:443 was resolved.977* IPv6: 2001:db8:1::3978* IPv4: 192.168.1.3979* Trying [2001:db8:1::3]:443...980* ALPN: curl offers h2,http/1.1981} [5 bytes data]982* TLSv1.3 (OUT), TLS handshake, Client hello (1):983} [1552 bytes data]984* SSL Trust Anchors:985* OpenSSL default paths (fallback)986{ [5 bytes data]987* TLSv1.3 (IN), TLS handshake, Server hello (2):988{ [1210 bytes data]989* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):990{ [1 bytes data]991* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):992{ [19 bytes data]993* TLSv1.3 (IN), TLS handshake, Certificate (11):994{ [1010 bytes data]995* TLSv1.3 (IN), TLS handshake, CERT verify (15):996{ [111 bytes data]997* TLSv1.3 (IN), TLS handshake, Finished (20):998{ [52 bytes data]999* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1000} [1 bytes data]1001* TLSv1.3 (OUT), TLS handshake, Finished (20):1002} [52 bytes data]1003* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1004* ALPN: server accepted h21005* Server certificate:1006* subject: CN=test.foo1007* start date: Sep 20 15:17:16 2026 GMT1008* expire date: Oct 20 15:17:16 2028 GMT1009* issuer: CN=minica root ca 10ef581010* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841011* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841012* subjectAltName: "test.foo" matches cert's "test.foo"1013* OpenSSL verify result: 131014* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1015* closing connection #01016curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1017More details here: https://curl.se/docs/sslcerts.html10181019curl failed to verify the legitimacy of the server and therefore could not1020establish a secure connection to it. To learn more about this situation and1021how to fix it, please visit the webpage mentioned above.1022* Host test.foo:443 was resolved.1023* IPv6: 2001:db8:1::31024* IPv4: 192.168.1.31025* Trying [2001:db8:1::3]:443...1026* ALPN: curl offers h2,http/1.11027} [5 bytes data]1028* TLSv1.3 (OUT), TLS handshake, Client hello (1):1029} [1552 bytes data]1030* SSL Trust Anchors:1031* OpenSSL default paths (fallback)1032{ [5 bytes data]1033* TLSv1.3 (IN), TLS handshake, Server hello (2):1034{ [1210 bytes data]1035* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1036{ [1 bytes data]1037* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1038{ [19 bytes data]1039* TLSv1.3 (IN), TLS handshake, Certificate (11):1040{ [1010 bytes data]1041* TLSv1.3 (IN), TLS handshake, CERT verify (15):1042{ [111 bytes data]1043* TLSv1.3 (IN), TLS handshake, Finished (20):1044{ [52 bytes data]1045* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1046} [1 bytes data]1047* TLSv1.3 (OUT), TLS handshake, Finished (20):1048} [52 bytes data]1049* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1050* ALPN: server accepted h21051* Server certificate:1052* subject: CN=test.foo1053* start date: Sep 20 15:17:16 2026 GMT1054* expire date: Oct 20 15:17:16 2028 GMT1055* issuer: CN=minica root ca 10ef581056* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841057* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841058* subjectAltName: "test.foo" matches cert's "test.foo"1059* OpenSSL verify result: 131060* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1061* closing connection #01062curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1063More details here: https://curl.se/docs/sslcerts.html10641065curl failed to verify the legitimacy of the server and therefore could not1066establish a secure connection to it. To learn more about this situation and1067how to fix it, please visit the webpage mentioned above.1068* Host test.foo:443 was resolved.1069* IPv6: 2001:db8:1::31070* IPv4: 192.168.1.31071* Trying [2001:db8:1::3]:443...1072* ALPN: curl offers h2,http/1.11073} [5 bytes data]1074* TLSv1.3 (OUT), TLS handshake, Client hello (1):1075} [1552 bytes data]1076* SSL Trust Anchors:1077* OpenSSL default paths (fallback)1078{ [5 bytes data]1079* TLSv1.3 (IN), TLS handshake, Server hello (2):1080{ [1210 bytes data]1081* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1082{ [1 bytes data]1083* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1084{ [19 bytes data]1085* TLSv1.3 (IN), TLS handshake, Certificate (11):1086{ [1010 bytes data]1087* TLSv1.3 (IN), TLS handshake, CERT verify (15):1088{ [112 bytes data]1089* TLSv1.3 (IN), TLS handshake, Finished (20):1090{ [52 bytes data]1091* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1092} [1 bytes data]1093* TLSv1.3 (OUT), TLS handshake, Finished (20):1094} [52 bytes data]1095* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1096* ALPN: server accepted h21097* Server certificate:1098* subject: CN=test.foo1099* start date: Sep 20 15:17:16 2026 GMT1100* expire date: Oct 20 15:17:16 2028 GMT1101* issuer: CN=minica root ca 10ef581102* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841103* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841104* subjectAltName: "test.foo" matches cert's "test.foo"1105* OpenSSL verify result: 131106* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1107* closing connection #01108curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1109More details here: https://curl.se/docs/sslcerts.html11101111curl failed to verify the legitimacy of the server and therefore could not1112establish a secure connection to it. To learn more about this situation and1113how to fix it, please visit the webpage mentioned above.1114* Host test.foo:443 was resolved.1115* IPv6: 2001:db8:1::31116* IPv4: 192.168.1.31117* Trying [2001:db8:1::3]:443...1118* ALPN: curl offers h2,http/1.11119} [5 bytes data]1120* TLSv1.3 (OUT), TLS handshake, Client hello (1):1121} [1552 bytes data]1122* SSL Trust Anchors:1123* OpenSSL default paths (fallback)1124{ [5 bytes data]1125* TLSv1.3 (IN), TLS handshake, Server hello (2):1126{ [1210 bytes data]1127* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1128{ [1 bytes data]1129* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1130{ [19 bytes data]1131* TLSv1.3 (IN), TLS handshake, Certificate (11):1132{ [1010 bytes data]1133* TLSv1.3 (IN), TLS handshake, CERT verify (15):1134{ [111 bytes data]1135* TLSv1.3 (IN), TLS handshake, Finished (20):1136{ [52 bytes data]1137* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1138} [1 bytes data]1139* TLSv1.3 (OUT), TLS handshake, Finished (20):1140} [52 bytes data]1141* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1142* ALPN: server accepted h21143* Server certificate:1144* subject: CN=test.foo1145* start date: Sep 20 15:17:16 2026 GMT1146* expire date: Oct 20 15:17:16 2028 GMT1147* issuer: CN=minica root ca 10ef581148* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841149* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841150* subjectAltName: "test.foo" matches cert's "test.foo"1151* OpenSSL verify result: 131152* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1153* closing connection #01154curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1155More details here: https://curl.se/docs/sslcerts.html11561157curl failed to verify the legitimacy of the server and therefore could not1158establish a secure connection to it. To learn more about this situation and1159how to fix it, please visit the webpage mentioned above.1160* Host test.foo:443 was resolved.1161* IPv6: 2001:db8:1::31162* IPv4: 192.168.1.31163* Trying [2001:db8:1::3]:443...1164* ALPN: curl offers h2,http/1.11165} [5 bytes data]1166* TLSv1.3 (OUT), TLS handshake, Client hello (1):1167} [1552 bytes data]1168* SSL Trust Anchors:1169* OpenSSL default paths (fallback)1170{ [5 bytes data]1171* TLSv1.3 (IN), TLS handshake, Server hello (2):1172{ [1210 bytes data]1173* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1174{ [1 bytes data]1175* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1176{ [19 bytes data]1177* TLSv1.3 (IN), TLS handshake, Certificate (11):1178{ [1010 bytes data]1179* TLSv1.3 (IN), TLS handshake, CERT verify (15):1180{ [111 bytes data]1181* TLSv1.3 (IN), TLS handshake, Finished (20):1182{ [52 bytes data]1183* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1184} [1 bytes data]1185* TLSv1.3 (OUT), TLS handshake, Finished (20):1186} [52 bytes data]1187* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1188* ALPN: server accepted h21189* Server certificate:1190* subject: CN=test.foo1191* start date: Sep 20 15:17:16 2026 GMT1192* expire date: Oct 20 15:17:16 2028 GMT1193* issuer: CN=minica root ca 10ef581194* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841195* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841196* subjectAltName: "test.foo" matches cert's "test.foo"1197* OpenSSL verify result: 131198* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1199* closing connection #01200curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1201More details here: https://curl.se/docs/sslcerts.html12021203curl failed to verify the legitimacy of the server and therefore could not1204establish a secure connection to it. To learn more about this situation and1205how to fix it, please visit the webpage mentioned above.1206* Trying [2001:db8:1::3]:443...1207* Host test.foo:443 was resolved.1208* IPv6: 2001:db8:1::31209* IPv4: 192.168.1.31210* ALPN: curl offers h2,http/1.11211} [5 bytes data]1212* TLSv1.3 (OUT), TLS handshake, Client hello (1):1213} [1552 bytes data]1214* SSL Trust Anchors:1215* OpenSSL default paths (fallback)1216{ [5 bytes data]1217* TLSv1.3 (IN), TLS handshake, Server hello (2):1218{ [1210 bytes data]1219* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1220{ [1 bytes data]1221* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1222{ [19 bytes data]1223* TLSv1.3 (IN), TLS handshake, Certificate (11):1224{ [1010 bytes data]1225* TLSv1.3 (IN), TLS handshake, CERT verify (15):1226{ [112 bytes data]1227* TLSv1.3 (IN), TLS handshake, Finished (20):1228{ [52 bytes data]1229* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1230} [1 bytes data]1231* TLSv1.3 (OUT), TLS handshake, Finished (20):1232} [52 bytes data]1233* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1234* ALPN: server accepted h21235* Server certificate:1236* subject: CN=test.foo1237* start date: Sep 20 15:17:16 2026 GMT1238* expire date: Oct 20 15:17:16 2028 GMT1239* issuer: CN=minica root ca 10ef581240* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841241* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841242* subjectAltName: "test.foo" matches cert's "test.foo"1243* OpenSSL verify result: 131244* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1245* closing connection #01246curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1247More details here: https://curl.se/docs/sslcerts.html12481249curl failed to verify the legitimacy of the server and therefore could not1250establish a secure connection to it. To learn more about this situation and1251how to fix it, please visit the webpage mentioned above.1252* Host test.foo:443 was resolved.1253* IPv6: 2001:db8:1::31254* IPv4: 192.168.1.31255* Trying [2001:db8:1::3]:443...1256* ALPN: curl offers h2,http/1.11257} [5 bytes data]1258* TLSv1.3 (OUT), TLS handshake, Client hello (1):1259} [1552 bytes data]1260* SSL Trust Anchors:1261* OpenSSL default paths (fallback)1262{ [5 bytes data]1263* TLSv1.3 (IN), TLS handshake, Server hello (2):1264{ [1210 bytes data]1265* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1266{ [1 bytes data]1267* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1268{ [19 bytes data]1269* TLSv1.3 (IN), TLS handshake, Certificate (11):1270{ [1010 bytes data]1271* TLSv1.3 (IN), TLS handshake, CERT verify (15):1272{ [111 bytes data]1273* TLSv1.3 (IN), TLS handshake, Finished (20):1274{ [52 bytes data]1275* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1276} [1 bytes data]1277* TLSv1.3 (OUT), TLS handshake, Finished (20):1278} [52 bytes data]1279* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1280* ALPN: server accepted h21281* Server certificate:1282* subject: CN=test.foo1283* start date: Sep 20 15:17:16 2026 GMT1284* expire date: Oct 20 15:17:16 2028 GMT1285* issuer: CN=minica root ca 10ef581286* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841287* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841288* subjectAltName: "test.foo" matches cert's "test.foo"1289* OpenSSL verify result: 131290* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1291* closing connection #01292curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1293More details here: https://curl.se/docs/sslcerts.html12941295curl failed to verify the legitimacy of the server and therefore could not1296establish a secure connection to it. To learn more about this situation and1297how to fix it, please visit the webpage mentioned above.1298* Host test.foo:443 was resolved.1299* IPv6: 2001:db8:1::31300* IPv4: 192.168.1.31301* Trying [2001:db8:1::3]:443...1302* ALPN: curl offers h2,http/1.11303} [5 bytes data]1304* TLSv1.3 (OUT), TLS handshake, Client hello (1):1305} [1552 bytes data]1306* SSL Trust Anchors:1307* OpenSSL default paths (fallback)1308{ [5 bytes data]1309* TLSv1.3 (IN), TLS handshake, Server hello (2):1310{ [1210 bytes data]1311* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1312{ [1 bytes data]1313* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1314{ [19 bytes data]1315* TLSv1.3 (IN), TLS handshake, Certificate (11):1316{ [1010 bytes data]1317* TLSv1.3 (IN), TLS handshake, CERT verify (15):1318{ [110 bytes data]1319* TLSv1.3 (IN), TLS handshake, Finished (20):1320{ [52 bytes data]1321* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1322} [1 bytes data]1323* TLSv1.3 (OUT), TLS handshake, Finished (20):1324} [52 bytes data]1325* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1326* ALPN: server accepted h21327* Server certificate:1328* subject: CN=test.foo1329* start date: Sep 20 15:17:16 2026 GMT1330* expire date: Oct 20 15:17:16 2028 GMT1331* issuer: CN=minica root ca 10ef581332* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841333* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841334* subjectAltName: "test.foo" matches cert's "test.foo"1335* OpenSSL verify result: 131336* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1337* closing connection #01338curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1339More details here: https://curl.se/docs/sslcerts.html13401341curl failed to verify the legitimacy of the server and therefore could not1342establish a secure connection to it. To learn more about this situation and1343how to fix it, please visit the webpage mentioned above.1344* Host test.foo:443 was resolved.1345* IPv6: 2001:db8:1::31346* IPv4: 192.168.1.31347* Trying [2001:db8:1::3]:443...1348* ALPN: curl offers h2,http/1.11349} [5 bytes data]1350* TLSv1.3 (OUT), TLS handshake, Client hello (1):1351} [1552 bytes data]1352* SSL Trust Anchors:1353* OpenSSL default paths (fallback)1354{ [5 bytes data]1355* TLSv1.3 (IN), TLS handshake, Server hello (2):1356{ [1210 bytes data]1357* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1358{ [1 bytes data]1359* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1360{ [19 bytes data]1361* TLSv1.3 (IN), TLS handshake, Certificate (11):1362{ [1010 bytes data]1363* TLSv1.3 (IN), TLS handshake, CERT verify (15):1364{ [112 bytes data]1365* TLSv1.3 (IN), TLS handshake, Finished (20):1366{ [52 bytes data]1367* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1368} [1 bytes data]1369* TLSv1.3 (OUT), TLS handshake, Finished (20):1370} [52 bytes data]1371* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1372* ALPN: server accepted h21373* Server certificate:1374* subject: CN=test.foo1375* start date: Sep 20 15:17:16 2026 GMT1376* expire date: Oct 20 15:17:16 2028 GMT1377* issuer: CN=minica root ca 10ef581378* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841379* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841380* subjectAltName: "test.foo" matches cert's "test.foo"1381* OpenSSL verify result: 131382* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1383* closing connection #01384curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1385More details here: https://curl.se/docs/sslcerts.html13861387curl failed to verify the legitimacy of the server and therefore could not1388establish a secure connection to it. To learn more about this situation and1389how to fix it, please visit the webpage mentioned above.1390* Host test.foo:443 was resolved.1391* IPv6: 2001:db8:1::31392* IPv4: 192.168.1.31393* Trying [2001:db8:1::3]:443...1394* ALPN: curl offers h2,http/1.11395} [5 bytes data]1396* TLSv1.3 (OUT), TLS handshake, Client hello (1):1397} [1552 bytes data]1398* SSL Trust Anchors:1399* OpenSSL default paths (fallback)1400{ [5 bytes data]1401* TLSv1.3 (IN), TLS handshake, Server hello (2):1402{ [1210 bytes data]1403* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1404{ [1 bytes data]1405* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1406{ [19 bytes data]1407* TLSv1.3 (IN), TLS handshake, Certificate (11):1408{ [1010 bytes data]1409* TLSv1.3 (IN), TLS handshake, CERT verify (15):1410{ [111 bytes data]1411* TLSv1.3 (IN), TLS handshake, Finished (20):1412{ [52 bytes data]1413* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1414} [1 bytes data]1415* TLSv1.3 (OUT), TLS handshake, Finished (20):1416} [52 bytes data]1417* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1418* ALPN: server accepted h21419* Server certificate:1420* subject: CN=test.foo1421* start date: Sep 20 15:17:16 2026 GMT1422* expire date: Oct 20 15:17:16 2028 GMT1423* issuer: CN=minica root ca 10ef581424* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841425* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841426* subjectAltName: "test.foo" matches cert's "test.foo"1427* OpenSSL verify result: 131428* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1429* closing connection #01430curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1431More details here: https://curl.se/docs/sslcerts.html14321433curl failed to verify the legitimacy of the server and therefore could not1434establish a secure connection to it. To learn more about this situation and1435how to fix it, please visit the webpage mentioned above.1436* Trying [2001:db8:1::3]:443...1437* Host test.foo:443 was resolved.1438* IPv6: 2001:db8:1::31439* IPv4: 192.168.1.31440* ALPN: curl offers h2,http/1.11441} [5 bytes data]1442* TLSv1.3 (OUT), TLS handshake, Client hello (1):1443} [1552 bytes data]1444* SSL Trust Anchors:1445* OpenSSL default paths (fallback)1446{ [5 bytes data]1447* TLSv1.3 (IN), TLS handshake, Server hello (2):1448{ [1210 bytes data]1449* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1450{ [1 bytes data]1451* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1452{ [19 bytes data]1453* TLSv1.3 (IN), TLS handshake, Certificate (11):1454{ [1010 bytes data]1455* TLSv1.3 (IN), TLS handshake, CERT verify (15):1456{ [110 bytes data]1457* TLSv1.3 (IN), TLS handshake, Finished (20):1458{ [52 bytes data]1459* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1460} [1 bytes data]1461* TLSv1.3 (OUT), TLS handshake, Finished (20):1462} [52 bytes data]1463* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1464* ALPN: server accepted h21465* Server certificate:1466* subject: CN=test.foo1467* start date: Sep 20 15:17:16 2026 GMT1468* expire date: Oct 20 15:17:16 2028 GMT1469* issuer: CN=minica root ca 10ef581470* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841471* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841472* subjectAltName: "test.foo" matches cert's "test.foo"1473* OpenSSL verify result: 131474* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1475* closing connection #01476curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1477More details here: https://curl.se/docs/sslcerts.html14781479curl failed to verify the legitimacy of the server and therefore could not1480establish a secure connection to it. To learn more about this situation and1481how to fix it, please visit the webpage mentioned above.1482* Host test.foo:443 was resolved.1483* IPv6: 2001:db8:1::31484* IPv4: 192.168.1.31485* Trying [2001:db8:1::3]:443...1486* ALPN: curl offers h2,http/1.11487} [5 bytes data]1488* TLSv1.3 (OUT), TLS handshake, Client hello (1):1489} [1552 bytes data]1490* SSL Trust Anchors:1491* OpenSSL default paths (fallback)1492{ [5 bytes data]1493* TLSv1.3 (IN), TLS handshake, Server hello (2):1494{ [1210 bytes data]1495* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1496{ [1 bytes data]1497* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1498{ [19 bytes data]1499* TLSv1.3 (IN), TLS handshake, Certificate (11):1500{ [1010 bytes data]1501* TLSv1.3 (IN), TLS handshake, CERT verify (15):1502{ [111 bytes data]1503* TLSv1.3 (IN), TLS handshake, Finished (20):1504{ [52 bytes data]1505* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1506} [1 bytes data]1507* TLSv1.3 (OUT), TLS handshake, Finished (20):1508} [52 bytes data]1509* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1510* ALPN: server accepted h21511* Server certificate:1512* subject: CN=test.foo1513* start date: Sep 20 15:17:16 2026 GMT1514* expire date: Oct 20 15:17:16 2028 GMT1515* issuer: CN=minica root ca 10ef581516* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841517* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841518* subjectAltName: "test.foo" matches cert's "test.foo"1519* OpenSSL verify result: 131520* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1521* closing connection #01522curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1523More details here: https://curl.se/docs/sslcerts.html15241525curl failed to verify the legitimacy of the server and therefore could not1526establish a secure connection to it. To learn more about this situation and1527how to fix it, please visit the webpage mentioned above.1528* Host test.foo:443 was resolved.1529* IPv6: 2001:db8:1::31530* IPv4: 192.168.1.31531* Trying [2001:db8:1::3]:443...1532* ALPN: curl offers h2,http/1.11533} [5 bytes data]1534* TLSv1.3 (OUT), TLS handshake, Client hello (1):1535} [1552 bytes data]1536* SSL Trust Anchors:1537* OpenSSL default paths (fallback)1538{ [5 bytes data]1539* TLSv1.3 (IN), TLS handshake, Server hello (2):1540{ [1210 bytes data]1541* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1542{ [1 bytes data]1543* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1544{ [19 bytes data]1545* TLSv1.3 (IN), TLS handshake, Certificate (11):1546{ [1010 bytes data]1547* TLSv1.3 (IN), TLS handshake, CERT verify (15):1548{ [110 bytes data]1549* TLSv1.3 (IN), TLS handshake, Finished (20):1550{ [52 bytes data]1551* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1552} [1 bytes data]1553* TLSv1.3 (OUT), TLS handshake, Finished (20):1554} [52 bytes data]1555* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1556* ALPN: server accepted h21557* Server certificate:1558* subject: CN=test.foo1559* start date: Sep 20 15:17:16 2026 GMT1560* expire date: Oct 20 15:17:16 2028 GMT1561* issuer: CN=minica root ca 10ef581562* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841563* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841564* subjectAltName: "test.foo" matches cert's "test.foo"1565* OpenSSL verify result: 131566* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1567* closing connection #01568curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1569More details here: https://curl.se/docs/sslcerts.html15701571curl failed to verify the legitimacy of the server and therefore could not1572establish a secure connection to it. To learn more about this situation and1573how to fix it, please visit the webpage mentioned above.1574* Trying [2001:db8:1::3]:443...1575* Host test.foo:443 was resolved.1576* IPv6: 2001:db8:1::31577* IPv4: 192.168.1.31578* ALPN: curl offers h2,http/1.11579} [5 bytes data]1580* TLSv1.3 (OUT), TLS handshake, Client hello (1):1581} [1552 bytes data]1582* SSL Trust Anchors:1583* OpenSSL default paths (fallback)1584{ [5 bytes data]1585* TLSv1.3 (IN), TLS handshake, Server hello (2):1586{ [1210 bytes data]1587* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1588{ [1 bytes data]1589* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1590{ [19 bytes data]1591* TLSv1.3 (IN), TLS handshake, Certificate (11):1592{ [1010 bytes data]1593* TLSv1.3 (IN), TLS handshake, CERT verify (15):1594{ [111 bytes data]1595* TLSv1.3 (IN), TLS handshake, Finished (20):1596{ [52 bytes data]1597* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1598} [1 bytes data]1599* TLSv1.3 (OUT), TLS handshake, Finished (20):1600} [52 bytes data]1601* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1602* ALPN: server accepted h21603* Server certificate:1604* subject: CN=test.foo1605* start date: Sep 20 15:17:16 2026 GMT1606* expire date: Oct 20 15:17:16 2028 GMT1607* issuer: CN=minica root ca 10ef581608* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841609* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841610* subjectAltName: "test.foo" matches cert's "test.foo"1611* OpenSSL verify result: 131612* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1613* closing connection #01614curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1615More details here: https://curl.se/docs/sslcerts.html16161617curl failed to verify the legitimacy of the server and therefore could not1618establish a secure connection to it. To learn more about this situation and1619how to fix it, please visit the webpage mentioned above.1620* Host test.foo:443 was resolved.1621* IPv6: 2001:db8:1::31622* IPv4: 192.168.1.31623* Trying [2001:db8:1::3]:443...1624* ALPN: curl offers h2,http/1.11625} [5 bytes data]1626* TLSv1.3 (OUT), TLS handshake, Client hello (1):1627} [1552 bytes data]1628* SSL Trust Anchors:1629* OpenSSL default paths (fallback)1630{ [5 bytes data]1631* TLSv1.3 (IN), TLS handshake, Server hello (2):1632{ [1210 bytes data]1633* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1634{ [1 bytes data]1635* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1636{ [19 bytes data]1637* TLSv1.3 (IN), TLS handshake, Certificate (11):1638{ [1010 bytes data]1639* TLSv1.3 (IN), TLS handshake, CERT verify (15):1640{ [111 bytes data]1641* TLSv1.3 (IN), TLS handshake, Finished (20):1642{ [52 bytes data]1643* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1644} [1 bytes data]1645* TLSv1.3 (OUT), TLS handshake, Finished (20):1646} [52 bytes data]1647* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1648* ALPN: server accepted h21649* Server certificate:1650* subject: CN=test.foo1651* start date: Sep 20 15:17:16 2026 GMT1652* expire date: Oct 20 15:17:16 2028 GMT1653* issuer: CN=minica root ca 10ef581654* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841655* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841656* subjectAltName: "test.foo" matches cert's "test.foo"1657* OpenSSL verify result: 131658* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1659* closing connection #01660curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1661More details here: https://curl.se/docs/sslcerts.html16621663curl failed to verify the legitimacy of the server and therefore could not1664establish a secure connection to it. To learn more about this situation and1665how to fix it, please visit the webpage mentioned above.1666* Host test.foo:443 was resolved.1667* IPv6: 2001:db8:1::31668* IPv4: 192.168.1.31669* Trying [2001:db8:1::3]:443...1670* ALPN: curl offers h2,http/1.11671} [5 bytes data]1672* TLSv1.3 (OUT), TLS handshake, Client hello (1):1673} [1552 bytes data]1674* SSL Trust Anchors:1675* OpenSSL default paths (fallback)1676{ [5 bytes data]1677* TLSv1.3 (IN), TLS handshake, Server hello (2):1678{ [1210 bytes data]1679* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1680{ [1 bytes data]1681* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1682{ [19 bytes data]1683* TLSv1.3 (IN), TLS handshake, Certificate (11):1684{ [1010 bytes data]1685* TLSv1.3 (IN), TLS handshake, CERT verify (15):1686{ [111 bytes data]1687* TLSv1.3 (IN), TLS handshake, Finished (20):1688{ [52 bytes data]1689* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1690} [1 bytes data]1691* TLSv1.3 (OUT), TLS handshake, Finished (20):1692} [52 bytes data]1693* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1694* ALPN: server accepted h21695* Server certificate:1696* subject: CN=test.foo1697* start date: Sep 20 15:17:16 2026 GMT1698* expire date: Oct 20 15:17:16 2028 GMT1699* issuer: CN=minica root ca 10ef581700* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841701* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841702* subjectAltName: "test.foo" matches cert's "test.foo"1703* OpenSSL verify result: 131704* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1705* closing connection #01706curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1707More details here: https://curl.se/docs/sslcerts.html17081709curl failed to verify the legitimacy of the server and therefore could not1710establish a secure connection to it. To learn more about this situation and1711how to fix it, please visit the webpage mentioned above.1712* Host test.foo:443 was resolved.1713* IPv6: 2001:db8:1::31714* IPv4: 192.168.1.31715* Trying [2001:db8:1::3]:443...1716* ALPN: curl offers h2,http/1.11717} [5 bytes data]1718* TLSv1.3 (OUT), TLS handshake, Client hello (1):1719} [1552 bytes data]1720* SSL Trust Anchors:1721* OpenSSL default paths (fallback)1722{ [5 bytes data]1723* TLSv1.3 (IN), TLS handshake, Server hello (2):1724{ [1210 bytes data]1725* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1726{ [1 bytes data]1727* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1728{ [19 bytes data]1729* TLSv1.3 (IN), TLS handshake, Certificate (11):1730{ [1010 bytes data]1731* TLSv1.3 (IN), TLS handshake, CERT verify (15):1732{ [112 bytes data]1733* TLSv1.3 (IN), TLS handshake, Finished (20):1734{ [52 bytes data]1735* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1736} [1 bytes data]1737* TLSv1.3 (OUT), TLS handshake, Finished (20):1738} [52 bytes data]1739* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1740* ALPN: server accepted h21741* Server certificate:1742* subject: CN=test.foo1743* start date: Sep 20 15:17:16 2026 GMT1744* expire date: Oct 20 15:17:16 2028 GMT1745* issuer: CN=minica root ca 10ef581746* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841747* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841748* subjectAltName: "test.foo" matches cert's "test.foo"1749* OpenSSL verify result: 131750* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1751* closing connection #01752curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1753More details here: https://curl.se/docs/sslcerts.html17541755curl failed to verify the legitimacy of the server and therefore could not1756establish a secure connection to it. To learn more about this situation and1757how to fix it, please visit the webpage mentioned above.1758* Host test.foo:443 was resolved.1759* IPv6: 2001:db8:1::31760* IPv4: 192.168.1.31761* Trying [2001:db8:1::3]:443...1762* ALPN: curl offers h2,http/1.11763} [5 bytes data]1764* TLSv1.3 (OUT), TLS handshake, Client hello (1):1765} [1552 bytes data]1766* SSL Trust Anchors:1767* OpenSSL default paths (fallback)1768{ [5 bytes data]1769* TLSv1.3 (IN), TLS handshake, Server hello (2):1770{ [1210 bytes data]1771* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1772{ [1 bytes data]1773* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1774{ [19 bytes data]1775* TLSv1.3 (IN), TLS handshake, Certificate (11):1776{ [1010 bytes data]1777* TLSv1.3 (IN), TLS handshake, CERT verify (15):1778{ [111 bytes data]1779* TLSv1.3 (IN), TLS handshake, Finished (20):1780{ [52 bytes data]1781* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1782} [1 bytes data]1783* TLSv1.3 (OUT), TLS handshake, Finished (20):1784} [52 bytes data]1785* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1786* ALPN: server accepted h21787* Server certificate:1788* subject: CN=test.foo1789* start date: Sep 20 15:17:16 2026 GMT1790* expire date: Oct 20 15:17:16 2028 GMT1791* issuer: CN=minica root ca 10ef581792* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841793* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841794* subjectAltName: "test.foo" matches cert's "test.foo"1795* OpenSSL verify result: 131796* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1797* closing connection #01798curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1799More details here: https://curl.se/docs/sslcerts.html18001801curl failed to verify the legitimacy of the server and therefore could not1802establish a secure connection to it. To learn more about this situation and1803how to fix it, please visit the webpage mentioned above.1804* Host test.foo:443 was resolved.1805* IPv6: 2001:db8:1::31806* IPv4: 192.168.1.31807* Trying [2001:db8:1::3]:443...1808* ALPN: curl offers h2,http/1.11809} [5 bytes data]1810* TLSv1.3 (OUT), TLS handshake, Client hello (1):1811} [1552 bytes data]1812* SSL Trust Anchors:1813* OpenSSL default paths (fallback)1814{ [5 bytes data]1815* TLSv1.3 (IN), TLS handshake, Server hello (2):1816{ [1210 bytes data]1817* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1818{ [1 bytes data]1819* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1820{ [19 bytes data]1821* TLSv1.3 (IN), TLS handshake, Certificate (11):1822{ [1010 bytes data]1823* TLSv1.3 (IN), TLS handshake, CERT verify (15):1824{ [111 bytes data]1825* TLSv1.3 (IN), TLS handshake, Finished (20):1826{ [52 bytes data]1827* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1828} [1 bytes data]1829* TLSv1.3 (OUT), TLS handshake, Finished (20):1830} [52 bytes data]1831* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1832* ALPN: server accepted h21833* Server certificate:1834* subject: CN=test.foo1835* start date: Sep 20 15:17:16 2026 GMT1836* expire date: Oct 20 15:17:16 2028 GMT1837* issuer: CN=minica root ca 10ef581838* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841839* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841840* subjectAltName: "test.foo" matches cert's "test.foo"1841* OpenSSL verify result: 131842* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1843* closing connection #01844curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1845More details here: https://curl.se/docs/sslcerts.html18461847curl failed to verify the legitimacy of the server and therefore could not1848establish a secure connection to it. To learn more about this situation and1849how to fix it, please visit the webpage mentioned above.1850* Host test.foo:443 was resolved.1851* IPv6: 2001:db8:1::31852* IPv4: 192.168.1.31853* Trying [2001:db8:1::3]:443...1854* ALPN: curl offers h2,http/1.11855} [5 bytes data]1856* TLSv1.3 (OUT), TLS handshake, Client hello (1):1857} [1552 bytes data]1858* SSL Trust Anchors:1859* OpenSSL default paths (fallback)1860{ [5 bytes data]1861* TLSv1.3 (IN), TLS handshake, Server hello (2):1862{ [1210 bytes data]1863* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1864{ [1 bytes data]1865* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1866{ [19 bytes data]1867* TLSv1.3 (IN), TLS handshake, Certificate (11):1868{ [1010 bytes data]1869* TLSv1.3 (IN), TLS handshake, CERT verify (15):1870{ [111 bytes data]1871* TLSv1.3 (IN), TLS handshake, Finished (20):1872{ [52 bytes data]1873* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1874} [1 bytes data]1875* TLSv1.3 (OUT), TLS handshake, Finished (20):1876} [52 bytes data]1877* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1878* ALPN: server accepted h21879* Server certificate:1880* subject: CN=test.foo1881* start date: Sep 20 15:17:16 2026 GMT1882* expire date: Oct 20 15:17:16 2028 GMT1883* issuer: CN=minica root ca 10ef581884* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841885* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841886* subjectAltName: "test.foo" matches cert's "test.foo"1887* OpenSSL verify result: 131888* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1889* closing connection #01890curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1891More details here: https://curl.se/docs/sslcerts.html18921893curl failed to verify the legitimacy of the server and therefore could not1894establish a secure connection to it. To learn more about this situation and1895how to fix it, please visit the webpage mentioned above.1896* Trying [2001:db8:1::3]:443...1897* Host test.foo:443 was resolved.1898* IPv6: 2001:db8:1::31899* IPv4: 192.168.1.31900* ALPN: curl offers h2,http/1.11901} [5 bytes data]1902* TLSv1.3 (OUT), TLS handshake, Client hello (1):1903} [1552 bytes data]1904* SSL Trust Anchors:1905* OpenSSL default paths (fallback)1906{ [5 bytes data]1907* TLSv1.3 (IN), TLS handshake, Server hello (2):1908{ [1210 bytes data]1909* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1910{ [1 bytes data]1911* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1912{ [19 bytes data]1913* TLSv1.3 (IN), TLS handshake, Certificate (11):1914{ [1010 bytes data]1915* TLSv1.3 (IN), TLS handshake, CERT verify (15):1916{ [111 bytes data]1917* TLSv1.3 (IN), TLS handshake, Finished (20):1918{ [52 bytes data]1919* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1920} [1 bytes data]1921* TLSv1.3 (OUT), TLS handshake, Finished (20):1922} [52 bytes data]1923* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1924* ALPN: server accepted h21925* Server certificate:1926* subject: CN=test.foo1927* start date: Sep 20 15:17:16 2026 GMT1928* expire date: Oct 20 15:17:16 2028 GMT1929* issuer: CN=minica root ca 10ef581930* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841931* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841932* subjectAltName: "test.foo" matches cert's "test.foo"1933* OpenSSL verify result: 131934* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1935* closing connection #01936curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1937More details here: https://curl.se/docs/sslcerts.html19381939curl failed to verify the legitimacy of the server and therefore could not1940establish a secure connection to it. To learn more about this situation and1941how to fix it, please visit the webpage mentioned above.1942* Host test.foo:443 was resolved.1943* IPv6: 2001:db8:1::31944* IPv4: 192.168.1.31945* Trying [2001:db8:1::3]:443...1946* ALPN: curl offers h2,http/1.11947} [5 bytes data]1948* TLSv1.3 (OUT), TLS handshake, Client hello (1):1949} [1552 bytes data]1950* SSL Trust Anchors:1951* OpenSSL default paths (fallback)1952{ [5 bytes data]1953* TLSv1.3 (IN), TLS handshake, Server hello (2):1954{ [1210 bytes data]1955* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):1956{ [1 bytes data]1957* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):1958{ [19 bytes data]1959* TLSv1.3 (IN), TLS handshake, Certificate (11):1960{ [1010 bytes data]1961* TLSv1.3 (IN), TLS handshake, CERT verify (15):1962{ [111 bytes data]1963* TLSv1.3 (IN), TLS handshake, Finished (20):1964{ [52 bytes data]1965* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):1966} [1 bytes data]1967* TLSv1.3 (OUT), TLS handshake, Finished (20):1968} [52 bytes data]1969* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey1970* ALPN: server accepted h21971* Server certificate:1972* subject: CN=test.foo1973* start date: Sep 20 15:17:16 2026 GMT1974* expire date: Oct 20 15:17:16 2028 GMT1975* issuer: CN=minica root ca 10ef581976* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841977* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA3841978* subjectAltName: "test.foo" matches cert's "test.foo"1979* OpenSSL verify result: 131980* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1981* closing connection #01982curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)1983More details here: https://curl.se/docs/sslcerts.html19841985curl failed to verify the legitimacy of the server and therefore could not1986establish a secure connection to it. To learn more about this situation and1987how to fix it, please visit the webpage mentioned above.1988* Host test.foo:443 was resolved.1989* IPv6: 2001:db8:1::31990* IPv4: 192.168.1.31991* Trying [2001:db8:1::3]:443...1992* ALPN: curl offers h2,http/1.11993} [5 bytes data]1994* TLSv1.3 (OUT), TLS handshake, Client hello (1):1995} [1552 bytes data]1996* SSL Trust Anchors:1997* OpenSSL default paths (fallback)1998{ [5 bytes data]1999* TLSv1.3 (IN), TLS handshake, Server hello (2):2000{ [1210 bytes data]
loading 35,097 hidden lines…
37098{ [1210 bytes data]37099* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37100{ [1 bytes data]37101* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37102{ [19 bytes data]37103* TLSv1.3 (IN), TLS handshake, Certificate (11):37104{ [1010 bytes data]37105* TLSv1.3 (IN), TLS handshake, CERT verify (15):37106{ [111 bytes data]37107* TLSv1.3 (IN), TLS handshake, Finished (20):37108{ [52 bytes data]37109* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37110} [1 bytes data]37111* TLSv1.3 (OUT), TLS handshake, Finished (20):37112} [52 bytes data]37113* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37114* ALPN: server accepted h237115* Server certificate:37116* subject: CN=test.foo37117* start date: Sep 20 15:17:16 2026 GMT37118* expire date: Oct 20 15:17:16 2028 GMT37119* issuer: CN=minica root ca 10ef5837120* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437121* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437122* subjectAltName: "test.foo" matches cert's "test.foo"37123* OpenSSL verify result: 1337124* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37125* closing connection #037126curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37127More details here: https://curl.se/docs/sslcerts.html3712837129curl failed to verify the legitimacy of the server and therefore could not37130establish a secure connection to it. To learn more about this situation and37131how to fix it, please visit the webpage mentioned above.37132* Host test.foo:443 was resolved.37133* IPv6: 2001:db8:1::337134* IPv4: 192.168.1.337135* Trying [2001:db8:1::3]:443...37136* ALPN: curl offers h2,http/1.137137} [5 bytes data]37138* TLSv1.3 (OUT), TLS handshake, Client hello (1):37139} [1552 bytes data]37140* SSL Trust Anchors:37141* OpenSSL default paths (fallback)37142{ [5 bytes data]37143* TLSv1.3 (IN), TLS handshake, Server hello (2):37144{ [1210 bytes data]37145* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37146{ [1 bytes data]37147* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37148{ [19 bytes data]37149* TLSv1.3 (IN), TLS handshake, Certificate (11):37150{ [1010 bytes data]37151* TLSv1.3 (IN), TLS handshake, CERT verify (15):37152{ [112 bytes data]37153* TLSv1.3 (IN), TLS handshake, Finished (20):37154{ [52 bytes data]37155* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37156} [1 bytes data]37157* TLSv1.3 (OUT), TLS handshake, Finished (20):37158} [52 bytes data]37159* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37160* ALPN: server accepted h237161* Server certificate:37162* subject: CN=test.foo37163* start date: Sep 20 15:17:16 2026 GMT37164* expire date: Oct 20 15:17:16 2028 GMT37165* issuer: CN=minica root ca 10ef5837166* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437167* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437168* subjectAltName: "test.foo" matches cert's "test.foo"37169* OpenSSL verify result: 1337170* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37171* closing connection #037172curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37173More details here: https://curl.se/docs/sslcerts.html3717437175curl failed to verify the legitimacy of the server and therefore could not37176establish a secure connection to it. To learn more about this situation and37177how to fix it, please visit the webpage mentioned above.37178* Host test.foo:443 was resolved.37179* IPv6: 2001:db8:1::337180* IPv4: 192.168.1.337181* Trying [2001:db8:1::3]:443...37182* ALPN: curl offers h2,http/1.137183} [5 bytes data]37184* TLSv1.3 (OUT), TLS handshake, Client hello (1):37185} [1552 bytes data]37186* SSL Trust Anchors:37187* OpenSSL default paths (fallback)37188{ [5 bytes data]37189* TLSv1.3 (IN), TLS handshake, Server hello (2):37190{ [1210 bytes data]37191* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37192{ [1 bytes data]37193* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37194{ [19 bytes data]37195* TLSv1.3 (IN), TLS handshake, Certificate (11):37196{ [1010 bytes data]37197* TLSv1.3 (IN), TLS handshake, CERT verify (15):37198{ [111 bytes data]37199* TLSv1.3 (IN), TLS handshake, Finished (20):37200{ [52 bytes data]37201* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37202} [1 bytes data]37203* TLSv1.3 (OUT), TLS handshake, Finished (20):37204} [52 bytes data]37205* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37206* ALPN: server accepted h237207* Server certificate:37208* subject: CN=test.foo37209* start date: Sep 20 15:17:16 2026 GMT37210* expire date: Oct 20 15:17:16 2028 GMT37211* issuer: CN=minica root ca 10ef5837212* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437213* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437214* subjectAltName: "test.foo" matches cert's "test.foo"37215* OpenSSL verify result: 1337216* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37217* closing connection #037218curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37219More details here: https://curl.se/docs/sslcerts.html3722037221curl failed to verify the legitimacy of the server and therefore could not37222establish a secure connection to it. To learn more about this situation and37223how to fix it, please visit the webpage mentioned above.37224* Host test.foo:443 was resolved.37225* IPv6: 2001:db8:1::337226* IPv4: 192.168.1.337227* Trying [2001:db8:1::3]:443...37228* ALPN: curl offers h2,http/1.137229} [5 bytes data]37230* TLSv1.3 (OUT), TLS handshake, Client hello (1):37231} [1552 bytes data]37232* SSL Trust Anchors:37233* OpenSSL default paths (fallback)37234{ [5 bytes data]37235* TLSv1.3 (IN), TLS handshake, Server hello (2):37236{ [1210 bytes data]37237* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37238{ [1 bytes data]37239* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37240{ [19 bytes data]37241* TLSv1.3 (IN), TLS handshake, Certificate (11):37242{ [1010 bytes data]37243* TLSv1.3 (IN), TLS handshake, CERT verify (15):37244{ [111 bytes data]37245* TLSv1.3 (IN), TLS handshake, Finished (20):37246{ [52 bytes data]37247* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37248} [1 bytes data]37249* TLSv1.3 (OUT), TLS handshake, Finished (20):37250} [52 bytes data]37251* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37252* ALPN: server accepted h237253* Server certificate:37254* subject: CN=test.foo37255* start date: Sep 20 15:17:16 2026 GMT37256* expire date: Oct 20 15:17:16 2028 GMT37257* issuer: CN=minica root ca 10ef5837258* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437259* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437260* subjectAltName: "test.foo" matches cert's "test.foo"37261* OpenSSL verify result: 1337262* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37263* closing connection #037264curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37265More details here: https://curl.se/docs/sslcerts.html3726637267curl failed to verify the legitimacy of the server and therefore could not37268establish a secure connection to it. To learn more about this situation and37269how to fix it, please visit the webpage mentioned above.37270* Host test.foo:443 was resolved.37271* IPv6: 2001:db8:1::337272* IPv4: 192.168.1.337273* Trying [2001:db8:1::3]:443...37274* ALPN: curl offers h2,http/1.137275} [5 bytes data]37276* TLSv1.3 (OUT), TLS handshake, Client hello (1):37277} [1552 bytes data]37278* SSL Trust Anchors:37279* OpenSSL default paths (fallback)37280{ [5 bytes data]37281* TLSv1.3 (IN), TLS handshake, Server hello (2):37282{ [1210 bytes data]37283* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37284{ [1 bytes data]37285* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37286{ [19 bytes data]37287* TLSv1.3 (IN), TLS handshake, Certificate (11):37288{ [1010 bytes data]37289* TLSv1.3 (IN), TLS handshake, CERT verify (15):37290{ [111 bytes data]37291* TLSv1.3 (IN), TLS handshake, Finished (20):37292{ [52 bytes data]37293* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37294} [1 bytes data]37295* TLSv1.3 (OUT), TLS handshake, Finished (20):37296} [52 bytes data]37297* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37298* ALPN: server accepted h237299* Server certificate:37300* subject: CN=test.foo37301* start date: Sep 20 15:17:16 2026 GMT37302* expire date: Oct 20 15:17:16 2028 GMT37303* issuer: CN=minica root ca 10ef5837304* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437305* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437306* subjectAltName: "test.foo" matches cert's "test.foo"37307* OpenSSL verify result: 1337308* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37309* closing connection #037310curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37311More details here: https://curl.se/docs/sslcerts.html3731237313curl failed to verify the legitimacy of the server and therefore could not37314establish a secure connection to it. To learn more about this situation and37315how to fix it, please visit the webpage mentioned above.37316* Host test.foo:443 was resolved.37317* IPv6: 2001:db8:1::337318* IPv4: 192.168.1.337319* Trying [2001:db8:1::3]:443...37320* ALPN: curl offers h2,http/1.137321} [5 bytes data]37322* TLSv1.3 (OUT), TLS handshake, Client hello (1):37323} [1552 bytes data]37324* SSL Trust Anchors:37325* OpenSSL default paths (fallback)37326{ [5 bytes data]37327* TLSv1.3 (IN), TLS handshake, Server hello (2):37328{ [1210 bytes data]37329* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37330{ [1 bytes data]37331* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37332{ [19 bytes data]37333* TLSv1.3 (IN), TLS handshake, Certificate (11):37334{ [1010 bytes data]37335* TLSv1.3 (IN), TLS handshake, CERT verify (15):37336{ [112 bytes data]37337* TLSv1.3 (IN), TLS handshake, Finished (20):37338{ [52 bytes data]37339* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37340} [1 bytes data]37341* TLSv1.3 (OUT), TLS handshake, Finished (20):37342} [52 bytes data]37343* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37344* ALPN: server accepted h237345* Server certificate:37346* subject: CN=test.foo37347* start date: Sep 20 15:17:16 2026 GMT37348* expire date: Oct 20 15:17:16 2028 GMT37349* issuer: CN=minica root ca 10ef5837350* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437351* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437352* subjectAltName: "test.foo" matches cert's "test.foo"37353* OpenSSL verify result: 1337354* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37355* closing connection #037356curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37357More details here: https://curl.se/docs/sslcerts.html3735837359curl failed to verify the legitimacy of the server and therefore could not37360establish a secure connection to it. To learn more about this situation and37361how to fix it, please visit the webpage mentioned above.37362* Host test.foo:443 was resolved.37363* IPv6: 2001:db8:1::337364* IPv4: 192.168.1.337365* Trying [2001:db8:1::3]:443...37366* ALPN: curl offers h2,http/1.137367} [5 bytes data]37368* TLSv1.3 (OUT), TLS handshake, Client hello (1):37369} [1552 bytes data]37370* SSL Trust Anchors:37371* OpenSSL default paths (fallback)37372{ [5 bytes data]37373* TLSv1.3 (IN), TLS handshake, Server hello (2):37374{ [1210 bytes data]37375* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37376{ [1 bytes data]37377* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37378{ [19 bytes data]37379* TLSv1.3 (IN), TLS handshake, Certificate (11):37380{ [1010 bytes data]37381* TLSv1.3 (IN), TLS handshake, CERT verify (15):37382{ [112 bytes data]37383* TLSv1.3 (IN), TLS handshake, Finished (20):37384{ [52 bytes data]37385* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37386} [1 bytes data]37387* TLSv1.3 (OUT), TLS handshake, Finished (20):37388} [52 bytes data]37389* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37390* ALPN: server accepted h237391* Server certificate:37392* subject: CN=test.foo37393* start date: Sep 20 15:17:16 2026 GMT37394* expire date: Oct 20 15:17:16 2028 GMT37395* issuer: CN=minica root ca 10ef5837396* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437397* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437398* subjectAltName: "test.foo" matches cert's "test.foo"37399* OpenSSL verify result: 1337400* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37401* closing connection #037402curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37403More details here: https://curl.se/docs/sslcerts.html3740437405curl failed to verify the legitimacy of the server and therefore could not37406establish a secure connection to it. To learn more about this situation and37407how to fix it, please visit the webpage mentioned above.37408* Trying [2001:db8:1::3]:443...37409* Host test.foo:443 was resolved.37410* IPv6: 2001:db8:1::337411* IPv4: 192.168.1.337412* ALPN: curl offers h2,http/1.137413} [5 bytes data]37414* TLSv1.3 (OUT), TLS handshake, Client hello (1):37415} [1552 bytes data]37416* SSL Trust Anchors:37417* OpenSSL default paths (fallback)37418{ [5 bytes data]37419* TLSv1.3 (IN), TLS handshake, Server hello (2):37420{ [1210 bytes data]37421* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37422{ [1 bytes data]37423* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37424{ [19 bytes data]37425* TLSv1.3 (IN), TLS handshake, Certificate (11):37426{ [1010 bytes data]37427* TLSv1.3 (IN), TLS handshake, CERT verify (15):37428{ [110 bytes data]37429* TLSv1.3 (IN), TLS handshake, Finished (20):37430{ [52 bytes data]37431* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37432} [1 bytes data]37433* TLSv1.3 (OUT), TLS handshake, Finished (20):37434} [52 bytes data]37435* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37436* ALPN: server accepted h237437* Server certificate:37438* subject: CN=test.foo37439* start date: Sep 20 15:17:16 2026 GMT37440* expire date: Oct 20 15:17:16 2028 GMT37441* issuer: CN=minica root ca 10ef5837442* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437443* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437444* subjectAltName: "test.foo" matches cert's "test.foo"37445* OpenSSL verify result: 1337446* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37447* closing connection #037448curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37449More details here: https://curl.se/docs/sslcerts.html3745037451curl failed to verify the legitimacy of the server and therefore could not37452establish a secure connection to it. To learn more about this situation and37453how to fix it, please visit the webpage mentioned above.37454* Host test.foo:443 was resolved.37455* IPv6: 2001:db8:1::337456* IPv4: 192.168.1.337457* Trying [2001:db8:1::3]:443...37458* ALPN: curl offers h2,http/1.137459} [5 bytes data]37460* TLSv1.3 (OUT), TLS handshake, Client hello (1):37461} [1552 bytes data]37462* SSL Trust Anchors:37463* OpenSSL default paths (fallback)37464{ [5 bytes data]37465* TLSv1.3 (IN), TLS handshake, Server hello (2):37466{ [1210 bytes data]37467* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37468{ [1 bytes data]37469* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37470{ [19 bytes data]37471* TLSv1.3 (IN), TLS handshake, Certificate (11):37472{ [1010 bytes data]37473* TLSv1.3 (IN), TLS handshake, CERT verify (15):37474{ [111 bytes data]37475* TLSv1.3 (IN), TLS handshake, Finished (20):37476{ [52 bytes data]37477* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37478} [1 bytes data]37479* TLSv1.3 (OUT), TLS handshake, Finished (20):37480} [52 bytes data]37481* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37482* ALPN: server accepted h237483* Server certificate:37484* subject: CN=test.foo37485* start date: Sep 20 15:17:16 2026 GMT37486* expire date: Oct 20 15:17:16 2028 GMT37487* issuer: CN=minica root ca 10ef5837488* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437489* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437490* subjectAltName: "test.foo" matches cert's "test.foo"37491* OpenSSL verify result: 1337492* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37493* closing connection #037494curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37495More details here: https://curl.se/docs/sslcerts.html3749637497curl failed to verify the legitimacy of the server and therefore could not37498establish a secure connection to it. To learn more about this situation and37499how to fix it, please visit the webpage mentioned above.37500* Host test.foo:443 was resolved.37501* IPv6: 2001:db8:1::337502* IPv4: 192.168.1.337503* Trying [2001:db8:1::3]:443...37504* ALPN: curl offers h2,http/1.137505} [5 bytes data]37506* TLSv1.3 (OUT), TLS handshake, Client hello (1):37507} [1552 bytes data]37508* SSL Trust Anchors:37509* OpenSSL default paths (fallback)37510{ [5 bytes data]37511* TLSv1.3 (IN), TLS handshake, Server hello (2):37512{ [1210 bytes data]37513* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37514{ [1 bytes data]37515* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37516{ [19 bytes data]37517* TLSv1.3 (IN), TLS handshake, Certificate (11):37518{ [1010 bytes data]37519* TLSv1.3 (IN), TLS handshake, CERT verify (15):37520{ [111 bytes data]37521* TLSv1.3 (IN), TLS handshake, Finished (20):37522{ [52 bytes data]37523* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37524} [1 bytes data]37525* TLSv1.3 (OUT), TLS handshake, Finished (20):37526} [52 bytes data]37527* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37528* ALPN: server accepted h237529* Server certificate:37530* subject: CN=test.foo37531* start date: Sep 20 15:17:16 2026 GMT37532* expire date: Oct 20 15:17:16 2028 GMT37533* issuer: CN=minica root ca 10ef5837534* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437535* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437536* subjectAltName: "test.foo" matches cert's "test.foo"37537* OpenSSL verify result: 1337538* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37539* closing connection #037540curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37541More details here: https://curl.se/docs/sslcerts.html3754237543curl failed to verify the legitimacy of the server and therefore could not37544establish a secure connection to it. To learn more about this situation and37545how to fix it, please visit the webpage mentioned above.37546* Trying [2001:db8:1::3]:443...37547* Host test.foo:443 was resolved.37548* IPv6: 2001:db8:1::337549* IPv4: 192.168.1.337550* ALPN: curl offers h2,http/1.137551} [5 bytes data]37552* TLSv1.3 (OUT), TLS handshake, Client hello (1):37553} [1552 bytes data]37554* SSL Trust Anchors:37555* OpenSSL default paths (fallback)37556{ [5 bytes data]37557* TLSv1.3 (IN), TLS handshake, Server hello (2):37558{ [1210 bytes data]37559* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37560{ [1 bytes data]37561* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37562{ [19 bytes data]37563* TLSv1.3 (IN), TLS handshake, Certificate (11):37564{ [1010 bytes data]37565* TLSv1.3 (IN), TLS handshake, CERT verify (15):37566{ [112 bytes data]37567* TLSv1.3 (IN), TLS handshake, Finished (20):37568{ [52 bytes data]37569* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37570} [1 bytes data]37571* TLSv1.3 (OUT), TLS handshake, Finished (20):37572} [52 bytes data]37573* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37574* ALPN: server accepted h237575* Server certificate:37576* subject: CN=test.foo37577* start date: Sep 20 15:17:16 2026 GMT37578* expire date: Oct 20 15:17:16 2028 GMT37579* issuer: CN=minica root ca 10ef5837580* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437581* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437582* subjectAltName: "test.foo" matches cert's "test.foo"37583* OpenSSL verify result: 1337584* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37585* closing connection #037586curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37587More details here: https://curl.se/docs/sslcerts.html3758837589curl failed to verify the legitimacy of the server and therefore could not37590establish a secure connection to it. To learn more about this situation and37591how to fix it, please visit the webpage mentioned above.37592* Trying [2001:db8:1::3]:443...37593* Host test.foo:443 was resolved.37594* IPv6: 2001:db8:1::337595* IPv4: 192.168.1.337596* ALPN: curl offers h2,http/1.137597} [5 bytes data]37598* TLSv1.3 (OUT), TLS handshake, Client hello (1):37599} [1552 bytes data]37600* SSL Trust Anchors:37601* OpenSSL default paths (fallback)37602{ [5 bytes data]37603* TLSv1.3 (IN), TLS handshake, Server hello (2):37604{ [1210 bytes data]37605* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37606{ [1 bytes data]37607* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37608{ [19 bytes data]37609* TLSv1.3 (IN), TLS handshake, Certificate (11):37610{ [1010 bytes data]37611* TLSv1.3 (IN), TLS handshake, CERT verify (15):37612{ [112 bytes data]37613* TLSv1.3 (IN), TLS handshake, Finished (20):37614{ [52 bytes data]37615* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37616} [1 bytes data]37617* TLSv1.3 (OUT), TLS handshake, Finished (20):37618} [52 bytes data]37619* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37620* ALPN: server accepted h237621* Server certificate:37622* subject: CN=test.foo37623* start date: Sep 20 15:17:16 2026 GMT37624* expire date: Oct 20 15:17:16 2028 GMT37625* issuer: CN=minica root ca 10ef5837626* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437627* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437628* subjectAltName: "test.foo" matches cert's "test.foo"37629* OpenSSL verify result: 1337630* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37631* closing connection #037632curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37633More details here: https://curl.se/docs/sslcerts.html3763437635curl failed to verify the legitimacy of the server and therefore could not37636establish a secure connection to it. To learn more about this situation and37637how to fix it, please visit the webpage mentioned above.37638* Host test.foo:443 was resolved.37639* IPv6: 2001:db8:1::337640* IPv4: 192.168.1.337641* Trying [2001:db8:1::3]:443...37642* ALPN: curl offers h2,http/1.137643} [5 bytes data]37644* TLSv1.3 (OUT), TLS handshake, Client hello (1):37645} [1552 bytes data]37646* SSL Trust Anchors:37647* OpenSSL default paths (fallback)37648{ [5 bytes data]37649* TLSv1.3 (IN), TLS handshake, Server hello (2):37650{ [1210 bytes data]37651* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37652{ [1 bytes data]37653* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37654{ [19 bytes data]37655* TLSv1.3 (IN), TLS handshake, Certificate (11):37656{ [1010 bytes data]37657* TLSv1.3 (IN), TLS handshake, CERT verify (15):37658{ [111 bytes data]37659* TLSv1.3 (IN), TLS handshake, Finished (20):37660{ [52 bytes data]37661* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37662} [1 bytes data]37663* TLSv1.3 (OUT), TLS handshake, Finished (20):37664} [52 bytes data]37665* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37666* ALPN: server accepted h237667* Server certificate:37668* subject: CN=test.foo37669* start date: Sep 20 15:17:16 2026 GMT37670* expire date: Oct 20 15:17:16 2028 GMT37671* issuer: CN=minica root ca 10ef5837672* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437673* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437674* subjectAltName: "test.foo" matches cert's "test.foo"37675* OpenSSL verify result: 1337676* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37677* closing connection #037678curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37679More details here: https://curl.se/docs/sslcerts.html3768037681curl failed to verify the legitimacy of the server and therefore could not37682establish a secure connection to it. To learn more about this situation and37683how to fix it, please visit the webpage mentioned above.37684* Host test.foo:443 was resolved.37685* IPv6: 2001:db8:1::337686* IPv4: 192.168.1.337687* Trying [2001:db8:1::3]:443...37688* ALPN: curl offers h2,http/1.137689} [5 bytes data]37690* TLSv1.3 (OUT), TLS handshake, Client hello (1):37691} [1552 bytes data]37692* SSL Trust Anchors:37693* OpenSSL default paths (fallback)37694{ [5 bytes data]37695* TLSv1.3 (IN), TLS handshake, Server hello (2):37696{ [1210 bytes data]37697* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37698{ [1 bytes data]37699* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37700{ [19 bytes data]37701* TLSv1.3 (IN), TLS handshake, Certificate (11):37702{ [1010 bytes data]37703* TLSv1.3 (IN), TLS handshake, CERT verify (15):37704{ [110 bytes data]37705* TLSv1.3 (IN), TLS handshake, Finished (20):37706{ [52 bytes data]37707* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37708} [1 bytes data]37709* TLSv1.3 (OUT), TLS handshake, Finished (20):37710} [52 bytes data]37711* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37712* ALPN: server accepted h237713* Server certificate:37714* subject: CN=test.foo37715* start date: Sep 20 15:17:16 2026 GMT37716* expire date: Oct 20 15:17:16 2028 GMT37717* issuer: CN=minica root ca 10ef5837718* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437719* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437720* subjectAltName: "test.foo" matches cert's "test.foo"37721* OpenSSL verify result: 1337722* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37723* closing connection #037724curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37725More details here: https://curl.se/docs/sslcerts.html3772637727curl failed to verify the legitimacy of the server and therefore could not37728establish a secure connection to it. To learn more about this situation and37729how to fix it, please visit the webpage mentioned above.37730* Host test.foo:443 was resolved.37731* IPv6: 2001:db8:1::337732* IPv4: 192.168.1.337733* Trying [2001:db8:1::3]:443...37734* ALPN: curl offers h2,http/1.137735} [5 bytes data]37736* TLSv1.3 (OUT), TLS handshake, Client hello (1):37737} [1552 bytes data]37738* SSL Trust Anchors:37739* OpenSSL default paths (fallback)37740{ [5 bytes data]37741* TLSv1.3 (IN), TLS handshake, Server hello (2):37742{ [1210 bytes data]37743* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37744{ [1 bytes data]37745* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37746{ [19 bytes data]37747* TLSv1.3 (IN), TLS handshake, Certificate (11):37748{ [1010 bytes data]37749* TLSv1.3 (IN), TLS handshake, CERT verify (15):37750{ [112 bytes data]37751* TLSv1.3 (IN), TLS handshake, Finished (20):37752{ [52 bytes data]37753* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37754} [1 bytes data]37755* TLSv1.3 (OUT), TLS handshake, Finished (20):37756} [52 bytes data]37757* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37758* ALPN: server accepted h237759* Server certificate:37760* subject: CN=test.foo37761* start date: Sep 20 15:17:16 2026 GMT37762* expire date: Oct 20 15:17:16 2028 GMT37763* issuer: CN=minica root ca 10ef5837764* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437765* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437766* subjectAltName: "test.foo" matches cert's "test.foo"37767* OpenSSL verify result: 1337768* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37769* closing connection #037770curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37771More details here: https://curl.se/docs/sslcerts.html3777237773curl failed to verify the legitimacy of the server and therefore could not37774establish a secure connection to it. To learn more about this situation and37775how to fix it, please visit the webpage mentioned above.37776* Host test.foo:443 was resolved.37777* IPv6: 2001:db8:1::337778* IPv4: 192.168.1.337779* Trying [2001:db8:1::3]:443...37780* ALPN: curl offers h2,http/1.137781} [5 bytes data]37782* TLSv1.3 (OUT), TLS handshake, Client hello (1):37783} [1552 bytes data]37784* SSL Trust Anchors:37785* OpenSSL default paths (fallback)37786{ [5 bytes data]37787* TLSv1.3 (IN), TLS handshake, Server hello (2):37788{ [1210 bytes data]37789* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37790{ [1 bytes data]37791* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37792{ [19 bytes data]37793* TLSv1.3 (IN), TLS handshake, Certificate (11):37794{ [1010 bytes data]37795* TLSv1.3 (IN), TLS handshake, CERT verify (15):37796{ [110 bytes data]37797* TLSv1.3 (IN), TLS handshake, Finished (20):37798{ [52 bytes data]37799* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37800} [1 bytes data]37801* TLSv1.3 (OUT), TLS handshake, Finished (20):37802} [52 bytes data]37803* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37804* ALPN: server accepted h237805* Server certificate:37806* subject: CN=test.foo37807* start date: Sep 20 15:17:16 2026 GMT37808* expire date: Oct 20 15:17:16 2028 GMT37809* issuer: CN=minica root ca 10ef5837810* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437811* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437812* subjectAltName: "test.foo" matches cert's "test.foo"37813* OpenSSL verify result: 1337814* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37815* closing connection #037816curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37817More details here: https://curl.se/docs/sslcerts.html3781837819curl failed to verify the legitimacy of the server and therefore could not37820establish a secure connection to it. To learn more about this situation and37821how to fix it, please visit the webpage mentioned above.37822* Host test.foo:443 was resolved.37823* IPv6: 2001:db8:1::337824* IPv4: 192.168.1.337825* Trying [2001:db8:1::3]:443...37826* ALPN: curl offers h2,http/1.137827} [5 bytes data]37828* TLSv1.3 (OUT), TLS handshake, Client hello (1):37829} [1552 bytes data]37830* SSL Trust Anchors:37831* OpenSSL default paths (fallback)37832{ [5 bytes data]37833* TLSv1.3 (IN), TLS handshake, Server hello (2):37834{ [1210 bytes data]37835* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37836{ [1 bytes data]37837* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37838{ [19 bytes data]37839* TLSv1.3 (IN), TLS handshake, Certificate (11):37840{ [1010 bytes data]37841* TLSv1.3 (IN), TLS handshake, CERT verify (15):37842{ [111 bytes data]37843* TLSv1.3 (IN), TLS handshake, Finished (20):37844{ [52 bytes data]37845* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37846} [1 bytes data]37847* TLSv1.3 (OUT), TLS handshake, Finished (20):37848} [52 bytes data]37849* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37850* ALPN: server accepted h237851* Server certificate:37852* subject: CN=test.foo37853* start date: Sep 20 15:17:16 2026 GMT37854* expire date: Oct 20 15:17:16 2028 GMT37855* issuer: CN=minica root ca 10ef5837856* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437857* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437858* subjectAltName: "test.foo" matches cert's "test.foo"37859* OpenSSL verify result: 1337860* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37861* closing connection #037862curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37863More details here: https://curl.se/docs/sslcerts.html3786437865curl failed to verify the legitimacy of the server and therefore could not37866establish a secure connection to it. To learn more about this situation and37867how to fix it, please visit the webpage mentioned above.37868* Host test.foo:443 was resolved.37869* IPv6: 2001:db8:1::337870* IPv4: 192.168.1.337871* Trying [2001:db8:1::3]:443...37872* ALPN: curl offers h2,http/1.137873} [5 bytes data]37874* TLSv1.3 (OUT), TLS handshake, Client hello (1):37875} [1552 bytes data]37876* SSL Trust Anchors:37877* OpenSSL default paths (fallback)37878{ [5 bytes data]37879* TLSv1.3 (IN), TLS handshake, Server hello (2):37880{ [1210 bytes data]37881* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37882{ [1 bytes data]37883* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37884{ [19 bytes data]37885* TLSv1.3 (IN), TLS handshake, Certificate (11):37886{ [1010 bytes data]37887* TLSv1.3 (IN), TLS handshake, CERT verify (15):37888{ [111 bytes data]37889* TLSv1.3 (IN), TLS handshake, Finished (20):37890{ [52 bytes data]37891* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37892} [1 bytes data]37893* TLSv1.3 (OUT), TLS handshake, Finished (20):37894} [52 bytes data]37895* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37896* ALPN: server accepted h237897* Server certificate:37898* subject: CN=test.foo37899* start date: Sep 20 15:17:16 2026 GMT37900* expire date: Oct 20 15:17:16 2028 GMT37901* issuer: CN=minica root ca 10ef5837902* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437903* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437904* subjectAltName: "test.foo" matches cert's "test.foo"37905* OpenSSL verify result: 1337906* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37907* closing connection #037908curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37909More details here: https://curl.se/docs/sslcerts.html3791037911curl failed to verify the legitimacy of the server and therefore could not37912establish a secure connection to it. To learn more about this situation and37913how to fix it, please visit the webpage mentioned above.37914* Host test.foo:443 was resolved.37915* IPv6: 2001:db8:1::337916* IPv4: 192.168.1.337917* Trying [2001:db8:1::3]:443...37918* ALPN: curl offers h2,http/1.137919} [5 bytes data]37920* TLSv1.3 (OUT), TLS handshake, Client hello (1):37921} [1552 bytes data]37922* SSL Trust Anchors:37923* OpenSSL default paths (fallback)37924{ [5 bytes data]37925* TLSv1.3 (IN), TLS handshake, Server hello (2):37926{ [1210 bytes data]37927* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37928{ [1 bytes data]37929* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37930{ [19 bytes data]37931* TLSv1.3 (IN), TLS handshake, Certificate (11):37932{ [1010 bytes data]37933* TLSv1.3 (IN), TLS handshake, CERT verify (15):37934{ [112 bytes data]37935* TLSv1.3 (IN), TLS handshake, Finished (20):37936{ [52 bytes data]37937* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37938} [1 bytes data]37939* TLSv1.3 (OUT), TLS handshake, Finished (20):37940} [52 bytes data]37941* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37942* ALPN: server accepted h237943* Server certificate:37944* subject: CN=test.foo37945* start date: Sep 20 15:17:16 2026 GMT37946* expire date: Oct 20 15:17:16 2028 GMT37947* issuer: CN=minica root ca 10ef5837948* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437949* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437950* subjectAltName: "test.foo" matches cert's "test.foo"37951* OpenSSL verify result: 1337952* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37953* closing connection #037954curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37955More details here: https://curl.se/docs/sslcerts.html3795637957curl failed to verify the legitimacy of the server and therefore could not37958establish a secure connection to it. To learn more about this situation and37959how to fix it, please visit the webpage mentioned above.37960* Host test.foo:443 was resolved.37961* IPv6: 2001:db8:1::337962* IPv4: 192.168.1.337963* Trying [2001:db8:1::3]:443...37964* ALPN: curl offers h2,http/1.137965} [5 bytes data]37966* TLSv1.3 (OUT), TLS handshake, Client hello (1):37967} [1552 bytes data]37968* SSL Trust Anchors:37969* OpenSSL default paths (fallback)37970{ [5 bytes data]37971* TLSv1.3 (IN), TLS handshake, Server hello (2):37972{ [1210 bytes data]37973* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):37974{ [1 bytes data]37975* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):37976{ [19 bytes data]37977* TLSv1.3 (IN), TLS handshake, Certificate (11):37978{ [1010 bytes data]37979* TLSv1.3 (IN), TLS handshake, CERT verify (15):37980{ [110 bytes data]37981* TLSv1.3 (IN), TLS handshake, Finished (20):37982{ [52 bytes data]37983* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):37984} [1 bytes data]37985* TLSv1.3 (OUT), TLS handshake, Finished (20):37986} [52 bytes data]37987* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey37988* ALPN: server accepted h237989* Server certificate:37990* subject: CN=test.foo37991* start date: Sep 20 15:17:16 2026 GMT37992* expire date: Oct 20 15:17:16 2028 GMT37993* issuer: CN=minica root ca 10ef5837994* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437995* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38437996* subjectAltName: "test.foo" matches cert's "test.foo"37997* OpenSSL verify result: 1337998* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)37999* closing connection #038000curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38001More details here: https://curl.se/docs/sslcerts.html3800238003curl failed to verify the legitimacy of the server and therefore could not38004establish a secure connection to it. To learn more about this situation and38005how to fix it, please visit the webpage mentioned above.38006* Host test.foo:443 was resolved.38007* IPv6: 2001:db8:1::338008* IPv4: 192.168.1.338009* Trying [2001:db8:1::3]:443...38010* ALPN: curl offers h2,http/1.138011} [5 bytes data]38012* TLSv1.3 (OUT), TLS handshake, Client hello (1):38013} [1552 bytes data]38014* SSL Trust Anchors:38015* OpenSSL default paths (fallback)38016{ [5 bytes data]38017* TLSv1.3 (IN), TLS handshake, Server hello (2):38018{ [1210 bytes data]38019* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38020{ [1 bytes data]38021* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38022{ [19 bytes data]38023* TLSv1.3 (IN), TLS handshake, Certificate (11):38024{ [1010 bytes data]38025* TLSv1.3 (IN), TLS handshake, CERT verify (15):38026{ [111 bytes data]38027* TLSv1.3 (IN), TLS handshake, Finished (20):38028{ [52 bytes data]38029* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38030} [1 bytes data]38031* TLSv1.3 (OUT), TLS handshake, Finished (20):38032} [52 bytes data]38033* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38034* ALPN: server accepted h238035* Server certificate:38036* subject: CN=test.foo38037* start date: Sep 20 15:17:16 2026 GMT38038* expire date: Oct 20 15:17:16 2028 GMT38039* issuer: CN=minica root ca 10ef5838040* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438041* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438042* subjectAltName: "test.foo" matches cert's "test.foo"38043* OpenSSL verify result: 1338044* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38045* closing connection #038046curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38047More details here: https://curl.se/docs/sslcerts.html3804838049curl failed to verify the legitimacy of the server and therefore could not38050establish a secure connection to it. To learn more about this situation and38051how to fix it, please visit the webpage mentioned above.38052* Host test.foo:443 was resolved.38053* IPv6: 2001:db8:1::338054* IPv4: 192.168.1.338055* Trying [2001:db8:1::3]:443...38056* ALPN: curl offers h2,http/1.138057} [5 bytes data]38058* TLSv1.3 (OUT), TLS handshake, Client hello (1):38059} [1552 bytes data]38060* SSL Trust Anchors:38061* OpenSSL default paths (fallback)38062{ [5 bytes data]38063* TLSv1.3 (IN), TLS handshake, Server hello (2):38064{ [1210 bytes data]38065* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38066{ [1 bytes data]38067* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38068{ [19 bytes data]38069* TLSv1.3 (IN), TLS handshake, Certificate (11):38070{ [1010 bytes data]38071* TLSv1.3 (IN), TLS handshake, CERT verify (15):38072{ [110 bytes data]38073* TLSv1.3 (IN), TLS handshake, Finished (20):38074{ [52 bytes data]38075* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38076} [1 bytes data]38077* TLSv1.3 (OUT), TLS handshake, Finished (20):38078} [52 bytes data]38079* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38080* ALPN: server accepted h238081* Server certificate:38082* subject: CN=test.foo38083* start date: Sep 20 15:17:16 2026 GMT38084* expire date: Oct 20 15:17:16 2028 GMT38085* issuer: CN=minica root ca 10ef5838086* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438087* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438088* subjectAltName: "test.foo" matches cert's "test.foo"38089* OpenSSL verify result: 1338090* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38091* closing connection #038092curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38093More details here: https://curl.se/docs/sslcerts.html3809438095curl failed to verify the legitimacy of the server and therefore could not38096establish a secure connection to it. To learn more about this situation and38097how to fix it, please visit the webpage mentioned above.38098* Host test.foo:443 was resolved.38099* IPv6: 2001:db8:1::338100* IPv4: 192.168.1.338101* Trying [2001:db8:1::3]:443...38102* ALPN: curl offers h2,http/1.138103} [5 bytes data]38104* TLSv1.3 (OUT), TLS handshake, Client hello (1):38105} [1552 bytes data]38106* SSL Trust Anchors:38107* OpenSSL default paths (fallback)38108{ [5 bytes data]38109* TLSv1.3 (IN), TLS handshake, Server hello (2):38110{ [1210 bytes data]38111* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38112{ [1 bytes data]38113* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38114{ [19 bytes data]38115* TLSv1.3 (IN), TLS handshake, Certificate (11):38116{ [1010 bytes data]38117* TLSv1.3 (IN), TLS handshake, CERT verify (15):38118{ [111 bytes data]38119* TLSv1.3 (IN), TLS handshake, Finished (20):38120{ [52 bytes data]38121* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38122} [1 bytes data]38123* TLSv1.3 (OUT), TLS handshake, Finished (20):38124} [52 bytes data]38125* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38126* ALPN: server accepted h238127* Server certificate:38128* subject: CN=test.foo38129* start date: Sep 20 15:17:16 2026 GMT38130* expire date: Oct 20 15:17:16 2028 GMT38131* issuer: CN=minica root ca 10ef5838132* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438133* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438134* subjectAltName: "test.foo" matches cert's "test.foo"38135* OpenSSL verify result: 1338136* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38137* closing connection #038138curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38139More details here: https://curl.se/docs/sslcerts.html3814038141curl failed to verify the legitimacy of the server and therefore could not38142establish a secure connection to it. To learn more about this situation and38143how to fix it, please visit the webpage mentioned above.38144* Host test.foo:443 was resolved.38145* IPv6: 2001:db8:1::338146* IPv4: 192.168.1.338147* Trying [2001:db8:1::3]:443...38148* ALPN: curl offers h2,http/1.138149} [5 bytes data]38150* TLSv1.3 (OUT), TLS handshake, Client hello (1):38151} [1552 bytes data]38152* SSL Trust Anchors:38153* OpenSSL default paths (fallback)38154{ [5 bytes data]38155* TLSv1.3 (IN), TLS handshake, Server hello (2):38156{ [1210 bytes data]38157* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38158{ [1 bytes data]38159* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38160{ [19 bytes data]38161* TLSv1.3 (IN), TLS handshake, Certificate (11):38162{ [1010 bytes data]38163* TLSv1.3 (IN), TLS handshake, CERT verify (15):38164{ [110 bytes data]38165* TLSv1.3 (IN), TLS handshake, Finished (20):38166{ [52 bytes data]38167* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38168} [1 bytes data]38169* TLSv1.3 (OUT), TLS handshake, Finished (20):38170} [52 bytes data]38171* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38172* ALPN: server accepted h238173* Server certificate:38174* subject: CN=test.foo38175* start date: Sep 20 15:17:16 2026 GMT38176* expire date: Oct 20 15:17:16 2028 GMT38177* issuer: CN=minica root ca 10ef5838178* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438179* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438180* subjectAltName: "test.foo" matches cert's "test.foo"38181* OpenSSL verify result: 1338182* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38183* closing connection #038184curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38185More details here: https://curl.se/docs/sslcerts.html3818638187curl failed to verify the legitimacy of the server and therefore could not38188establish a secure connection to it. To learn more about this situation and38189how to fix it, please visit the webpage mentioned above.38190* Host test.foo:443 was resolved.38191* IPv6: 2001:db8:1::338192* IPv4: 192.168.1.338193* Trying [2001:db8:1::3]:443...38194* ALPN: curl offers h2,http/1.138195} [5 bytes data]38196* TLSv1.3 (OUT), TLS handshake, Client hello (1):38197} [1552 bytes data]38198* SSL Trust Anchors:38199* OpenSSL default paths (fallback)38200{ [5 bytes data]38201* TLSv1.3 (IN), TLS handshake, Server hello (2):38202{ [1210 bytes data]38203* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38204{ [1 bytes data]38205* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38206{ [19 bytes data]38207* TLSv1.3 (IN), TLS handshake, Certificate (11):38208{ [1010 bytes data]38209* TLSv1.3 (IN), TLS handshake, CERT verify (15):38210{ [111 bytes data]38211* TLSv1.3 (IN), TLS handshake, Finished (20):38212{ [52 bytes data]38213* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38214} [1 bytes data]38215* TLSv1.3 (OUT), TLS handshake, Finished (20):38216} [52 bytes data]38217* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38218* ALPN: server accepted h238219* Server certificate:38220* subject: CN=test.foo38221* start date: Sep 20 15:17:16 2026 GMT38222* expire date: Oct 20 15:17:16 2028 GMT38223* issuer: CN=minica root ca 10ef5838224* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438225* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438226* subjectAltName: "test.foo" matches cert's "test.foo"38227* OpenSSL verify result: 1338228* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38229* closing connection #038230curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38231More details here: https://curl.se/docs/sslcerts.html3823238233curl failed to verify the legitimacy of the server and therefore could not38234establish a secure connection to it. To learn more about this situation and38235how to fix it, please visit the webpage mentioned above.38236* Host test.foo:443 was resolved.38237* IPv6: 2001:db8:1::338238* IPv4: 192.168.1.338239* Trying [2001:db8:1::3]:443...38240* ALPN: curl offers h2,http/1.138241} [5 bytes data]38242* TLSv1.3 (OUT), TLS handshake, Client hello (1):38243} [1552 bytes data]38244* SSL Trust Anchors:38245* OpenSSL default paths (fallback)38246{ [5 bytes data]38247* TLSv1.3 (IN), TLS handshake, Server hello (2):38248{ [1210 bytes data]38249* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38250{ [1 bytes data]38251* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38252{ [19 bytes data]38253* TLSv1.3 (IN), TLS handshake, Certificate (11):38254{ [1010 bytes data]38255* TLSv1.3 (IN), TLS handshake, CERT verify (15):38256{ [110 bytes data]38257* TLSv1.3 (IN), TLS handshake, Finished (20):38258{ [52 bytes data]38259* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38260} [1 bytes data]38261* TLSv1.3 (OUT), TLS handshake, Finished (20):38262} [52 bytes data]38263* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38264* ALPN: server accepted h238265* Server certificate:38266* subject: CN=test.foo38267* start date: Sep 20 15:17:16 2026 GMT38268* expire date: Oct 20 15:17:16 2028 GMT38269* issuer: CN=minica root ca 10ef5838270* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438271* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438272* subjectAltName: "test.foo" matches cert's "test.foo"38273* OpenSSL verify result: 1338274* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38275* closing connection #038276curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38277More details here: https://curl.se/docs/sslcerts.html3827838279curl failed to verify the legitimacy of the server and therefore could not38280establish a secure connection to it. To learn more about this situation and38281how to fix it, please visit the webpage mentioned above.38282* Host test.foo:443 was resolved.38283* IPv6: 2001:db8:1::338284* IPv4: 192.168.1.338285* Trying [2001:db8:1::3]:443...38286* ALPN: curl offers h2,http/1.138287} [5 bytes data]38288* TLSv1.3 (OUT), TLS handshake, Client hello (1):38289} [1552 bytes data]38290* SSL Trust Anchors:38291* OpenSSL default paths (fallback)38292{ [5 bytes data]38293* TLSv1.3 (IN), TLS handshake, Server hello (2):38294{ [1210 bytes data]38295* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38296{ [1 bytes data]38297* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38298{ [19 bytes data]38299* TLSv1.3 (IN), TLS handshake, Certificate (11):38300{ [1010 bytes data]38301* TLSv1.3 (IN), TLS handshake, CERT verify (15):38302{ [112 bytes data]38303* TLSv1.3 (IN), TLS handshake, Finished (20):38304{ [52 bytes data]38305* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38306} [1 bytes data]38307* TLSv1.3 (OUT), TLS handshake, Finished (20):38308} [52 bytes data]38309* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38310* ALPN: server accepted h238311* Server certificate:38312* subject: CN=test.foo38313* start date: Sep 20 15:17:16 2026 GMT38314* expire date: Oct 20 15:17:16 2028 GMT38315* issuer: CN=minica root ca 10ef5838316* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438317* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438318* subjectAltName: "test.foo" matches cert's "test.foo"38319* OpenSSL verify result: 1338320* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38321* closing connection #038322curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38323More details here: https://curl.se/docs/sslcerts.html3832438325curl failed to verify the legitimacy of the server and therefore could not38326establish a secure connection to it. To learn more about this situation and38327how to fix it, please visit the webpage mentioned above.38328* Host test.foo:443 was resolved.38329* IPv6: 2001:db8:1::338330* IPv4: 192.168.1.338331* Trying [2001:db8:1::3]:443...38332* ALPN: curl offers h2,http/1.138333} [5 bytes data]38334* TLSv1.3 (OUT), TLS handshake, Client hello (1):38335} [1552 bytes data]38336* SSL Trust Anchors:38337* OpenSSL default paths (fallback)38338{ [5 bytes data]38339* TLSv1.3 (IN), TLS handshake, Server hello (2):38340{ [1210 bytes data]38341* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38342{ [1 bytes data]38343* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38344{ [19 bytes data]38345* TLSv1.3 (IN), TLS handshake, Certificate (11):38346{ [1010 bytes data]38347* TLSv1.3 (IN), TLS handshake, CERT verify (15):38348{ [110 bytes data]38349* TLSv1.3 (IN), TLS handshake, Finished (20):38350{ [52 bytes data]38351* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38352} [1 bytes data]38353* TLSv1.3 (OUT), TLS handshake, Finished (20):38354} [52 bytes data]38355* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38356* ALPN: server accepted h238357* Server certificate:38358* subject: CN=test.foo38359* start date: Sep 20 15:17:16 2026 GMT38360* expire date: Oct 20 15:17:16 2028 GMT38361* issuer: CN=minica root ca 10ef5838362* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438363* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438364* subjectAltName: "test.foo" matches cert's "test.foo"38365* OpenSSL verify result: 1338366* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38367* closing connection #038368curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38369More details here: https://curl.se/docs/sslcerts.html3837038371curl failed to verify the legitimacy of the server and therefore could not38372establish a secure connection to it. To learn more about this situation and38373how to fix it, please visit the webpage mentioned above.38374* Host test.foo:443 was resolved.38375* IPv6: 2001:db8:1::338376* IPv4: 192.168.1.338377* Trying [2001:db8:1::3]:443...38378* ALPN: curl offers h2,http/1.138379} [5 bytes data]38380* TLSv1.3 (OUT), TLS handshake, Client hello (1):38381} [1552 bytes data]38382* SSL Trust Anchors:38383* OpenSSL default paths (fallback)38384{ [5 bytes data]38385* TLSv1.3 (IN), TLS handshake, Server hello (2):38386{ [1210 bytes data]38387* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38388{ [1 bytes data]38389* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38390{ [19 bytes data]38391* TLSv1.3 (IN), TLS handshake, Certificate (11):38392{ [1010 bytes data]38393* TLSv1.3 (IN), TLS handshake, CERT verify (15):38394{ [112 bytes data]38395* TLSv1.3 (IN), TLS handshake, Finished (20):38396{ [52 bytes data]38397* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38398} [1 bytes data]38399* TLSv1.3 (OUT), TLS handshake, Finished (20):38400} [52 bytes data]38401* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38402* ALPN: server accepted h238403* Server certificate:38404* subject: CN=test.foo38405* start date: Sep 20 15:17:16 2026 GMT38406* expire date: Oct 20 15:17:16 2028 GMT38407* issuer: CN=minica root ca 10ef5838408* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438409* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438410* subjectAltName: "test.foo" matches cert's "test.foo"38411* OpenSSL verify result: 1338412* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38413* closing connection #038414curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38415More details here: https://curl.se/docs/sslcerts.html3841638417curl failed to verify the legitimacy of the server and therefore could not38418establish a secure connection to it. To learn more about this situation and38419how to fix it, please visit the webpage mentioned above.38420* Host test.foo:443 was resolved.38421* IPv6: 2001:db8:1::338422* IPv4: 192.168.1.338423* Trying [2001:db8:1::3]:443...38424* ALPN: curl offers h2,http/1.138425} [5 bytes data]38426* TLSv1.3 (OUT), TLS handshake, Client hello (1):38427} [1552 bytes data]38428* SSL Trust Anchors:38429* OpenSSL default paths (fallback)38430{ [5 bytes data]38431* TLSv1.3 (IN), TLS handshake, Server hello (2):38432{ [1210 bytes data]38433* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38434{ [1 bytes data]38435* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38436{ [19 bytes data]38437* TLSv1.3 (IN), TLS handshake, Certificate (11):38438{ [1010 bytes data]38439* TLSv1.3 (IN), TLS handshake, CERT verify (15):38440{ [111 bytes data]38441* TLSv1.3 (IN), TLS handshake, Finished (20):38442{ [52 bytes data]38443* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38444} [1 bytes data]38445* TLSv1.3 (OUT), TLS handshake, Finished (20):38446} [52 bytes data]38447* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38448* ALPN: server accepted h238449* Server certificate:38450* subject: CN=test.foo38451* start date: Sep 20 15:17:16 2026 GMT38452* expire date: Oct 20 15:17:16 2028 GMT38453* issuer: CN=minica root ca 10ef5838454* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438455* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438456* subjectAltName: "test.foo" matches cert's "test.foo"38457* OpenSSL verify result: 1338458* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38459* closing connection #038460curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38461More details here: https://curl.se/docs/sslcerts.html3846238463curl failed to verify the legitimacy of the server and therefore could not38464establish a secure connection to it. To learn more about this situation and38465how to fix it, please visit the webpage mentioned above.38466* Host test.foo:443 was resolved.38467* IPv6: 2001:db8:1::338468* IPv4: 192.168.1.338469* Trying [2001:db8:1::3]:443...38470* ALPN: curl offers h2,http/1.138471} [5 bytes data]38472* TLSv1.3 (OUT), TLS handshake, Client hello (1):38473} [1552 bytes data]38474* SSL Trust Anchors:38475* OpenSSL default paths (fallback)38476{ [5 bytes data]38477* TLSv1.3 (IN), TLS handshake, Server hello (2):38478{ [1210 bytes data]38479* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38480{ [1 bytes data]38481* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38482{ [19 bytes data]38483* TLSv1.3 (IN), TLS handshake, Certificate (11):38484{ [1010 bytes data]38485* TLSv1.3 (IN), TLS handshake, CERT verify (15):38486{ [111 bytes data]38487* TLSv1.3 (IN), TLS handshake, Finished (20):38488{ [52 bytes data]38489* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38490} [1 bytes data]38491* TLSv1.3 (OUT), TLS handshake, Finished (20):38492} [52 bytes data]38493* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38494* ALPN: server accepted h238495* Server certificate:38496* subject: CN=test.foo38497* start date: Sep 20 15:17:16 2026 GMT38498* expire date: Oct 20 15:17:16 2028 GMT38499* issuer: CN=minica root ca 10ef5838500* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438501* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438502* subjectAltName: "test.foo" matches cert's "test.foo"38503* OpenSSL verify result: 1338504* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38505* closing connection #038506curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38507More details here: https://curl.se/docs/sslcerts.html3850838509curl failed to verify the legitimacy of the server and therefore could not38510establish a secure connection to it. To learn more about this situation and38511how to fix it, please visit the webpage mentioned above.38512* Host test.foo:443 was resolved.38513* IPv6: 2001:db8:1::338514* IPv4: 192.168.1.338515* Trying [2001:db8:1::3]:443...38516* ALPN: curl offers h2,http/1.138517} [5 bytes data]38518* TLSv1.3 (OUT), TLS handshake, Client hello (1):38519} [1552 bytes data]38520* SSL Trust Anchors:38521* OpenSSL default paths (fallback)38522{ [5 bytes data]38523* TLSv1.3 (IN), TLS handshake, Server hello (2):38524{ [1210 bytes data]38525* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38526{ [1 bytes data]38527* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38528{ [19 bytes data]38529* TLSv1.3 (IN), TLS handshake, Certificate (11):38530{ [1010 bytes data]38531* TLSv1.3 (IN), TLS handshake, CERT verify (15):38532{ [112 bytes data]38533* TLSv1.3 (IN), TLS handshake, Finished (20):38534{ [52 bytes data]38535* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38536} [1 bytes data]38537* TLSv1.3 (OUT), TLS handshake, Finished (20):38538} [52 bytes data]38539* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38540* ALPN: server accepted h238541* Server certificate:38542* subject: CN=test.foo38543* start date: Sep 20 15:17:16 2026 GMT38544* expire date: Oct 20 15:17:16 2028 GMT38545* issuer: CN=minica root ca 10ef5838546* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438547* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438548* subjectAltName: "test.foo" matches cert's "test.foo"38549* OpenSSL verify result: 1338550* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38551* closing connection #038552curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38553More details here: https://curl.se/docs/sslcerts.html3855438555curl failed to verify the legitimacy of the server and therefore could not38556establish a secure connection to it. To learn more about this situation and38557how to fix it, please visit the webpage mentioned above.38558* Host test.foo:443 was resolved.38559* IPv6: 2001:db8:1::338560* IPv4: 192.168.1.338561* Trying [2001:db8:1::3]:443...38562* ALPN: curl offers h2,http/1.138563} [5 bytes data]38564* TLSv1.3 (OUT), TLS handshake, Client hello (1):38565} [1552 bytes data]38566* SSL Trust Anchors:38567* OpenSSL default paths (fallback)38568{ [5 bytes data]38569* TLSv1.3 (IN), TLS handshake, Server hello (2):38570{ [1210 bytes data]38571* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38572{ [1 bytes data]38573* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38574{ [19 bytes data]38575* TLSv1.3 (IN), TLS handshake, Certificate (11):38576{ [1010 bytes data]38577* TLSv1.3 (IN), TLS handshake, CERT verify (15):38578{ [111 bytes data]38579* TLSv1.3 (IN), TLS handshake, Finished (20):38580{ [52 bytes data]38581* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38582} [1 bytes data]38583* TLSv1.3 (OUT), TLS handshake, Finished (20):38584} [52 bytes data]38585* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38586* ALPN: server accepted h238587* Server certificate:38588* subject: CN=test.foo38589* start date: Sep 20 15:17:16 2026 GMT38590* expire date: Oct 20 15:17:16 2028 GMT38591* issuer: CN=minica root ca 10ef5838592* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438593* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438594* subjectAltName: "test.foo" matches cert's "test.foo"38595* OpenSSL verify result: 1338596* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38597* closing connection #038598curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38599More details here: https://curl.se/docs/sslcerts.html3860038601curl failed to verify the legitimacy of the server and therefore could not38602establish a secure connection to it. To learn more about this situation and38603how to fix it, please visit the webpage mentioned above.38604* Host test.foo:443 was resolved.38605* IPv6: 2001:db8:1::338606* IPv4: 192.168.1.338607* Trying [2001:db8:1::3]:443...38608* ALPN: curl offers h2,http/1.138609} [5 bytes data]38610* TLSv1.3 (OUT), TLS handshake, Client hello (1):38611} [1552 bytes data]38612* SSL Trust Anchors:38613* OpenSSL default paths (fallback)38614{ [5 bytes data]38615* TLSv1.3 (IN), TLS handshake, Server hello (2):38616{ [1210 bytes data]38617* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38618{ [1 bytes data]38619* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38620{ [19 bytes data]38621* TLSv1.3 (IN), TLS handshake, Certificate (11):38622{ [1010 bytes data]38623* TLSv1.3 (IN), TLS handshake, CERT verify (15):38624{ [111 bytes data]38625* TLSv1.3 (IN), TLS handshake, Finished (20):38626{ [52 bytes data]38627* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38628} [1 bytes data]38629* TLSv1.3 (OUT), TLS handshake, Finished (20):38630} [52 bytes data]38631* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38632* ALPN: server accepted h238633* Server certificate:38634* subject: CN=test.foo38635* start date: Sep 20 15:17:16 2026 GMT38636* expire date: Oct 20 15:17:16 2028 GMT38637* issuer: CN=minica root ca 10ef5838638* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438639* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438640* subjectAltName: "test.foo" matches cert's "test.foo"38641* OpenSSL verify result: 1338642* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38643* closing connection #038644curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38645More details here: https://curl.se/docs/sslcerts.html3864638647curl failed to verify the legitimacy of the server and therefore could not38648establish a secure connection to it. To learn more about this situation and38649how to fix it, please visit the webpage mentioned above.38650* Host test.foo:443 was resolved.38651* IPv6: 2001:db8:1::338652* IPv4: 192.168.1.338653* Trying [2001:db8:1::3]:443...38654* ALPN: curl offers h2,http/1.138655} [5 bytes data]38656* TLSv1.3 (OUT), TLS handshake, Client hello (1):38657} [1552 bytes data]38658* SSL Trust Anchors:38659* OpenSSL default paths (fallback)38660{ [5 bytes data]38661* TLSv1.3 (IN), TLS handshake, Server hello (2):38662{ [1210 bytes data]38663* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38664{ [1 bytes data]38665* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38666{ [19 bytes data]38667* TLSv1.3 (IN), TLS handshake, Certificate (11):38668{ [1010 bytes data]38669* TLSv1.3 (IN), TLS handshake, CERT verify (15):38670{ [111 bytes data]38671* TLSv1.3 (IN), TLS handshake, Finished (20):38672{ [52 bytes data]38673* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38674} [1 bytes data]38675* TLSv1.3 (OUT), TLS handshake, Finished (20):38676} [52 bytes data]38677* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38678* ALPN: server accepted h238679* Server certificate:38680* subject: CN=test.foo38681* start date: Sep 20 15:17:16 2026 GMT38682* expire date: Oct 20 15:17:16 2028 GMT38683* issuer: CN=minica root ca 10ef5838684* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438685* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438686* subjectAltName: "test.foo" matches cert's "test.foo"38687* OpenSSL verify result: 1338688* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38689* closing connection #038690curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38691More details here: https://curl.se/docs/sslcerts.html3869238693curl failed to verify the legitimacy of the server and therefore could not38694establish a secure connection to it. To learn more about this situation and38695how to fix it, please visit the webpage mentioned above.38696* Host test.foo:443 was resolved.38697* IPv6: 2001:db8:1::338698* IPv4: 192.168.1.338699* Trying [2001:db8:1::3]:443...38700* ALPN: curl offers h2,http/1.138701} [5 bytes data]38702* TLSv1.3 (OUT), TLS handshake, Client hello (1):38703} [1552 bytes data]38704* SSL Trust Anchors:38705* OpenSSL default paths (fallback)38706{ [5 bytes data]38707* TLSv1.3 (IN), TLS handshake, Server hello (2):38708{ [1210 bytes data]38709* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38710{ [1 bytes data]38711* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38712{ [19 bytes data]38713* TLSv1.3 (IN), TLS handshake, Certificate (11):38714{ [1010 bytes data]38715* TLSv1.3 (IN), TLS handshake, CERT verify (15):38716{ [110 bytes data]38717* TLSv1.3 (IN), TLS handshake, Finished (20):38718{ [52 bytes data]38719* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38720} [1 bytes data]38721* TLSv1.3 (OUT), TLS handshake, Finished (20):38722} [52 bytes data]38723* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38724* ALPN: server accepted h238725* Server certificate:38726* subject: CN=test.foo38727* start date: Sep 20 15:17:16 2026 GMT38728* expire date: Oct 20 15:17:16 2028 GMT38729* issuer: CN=minica root ca 10ef5838730* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438731* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438732* subjectAltName: "test.foo" matches cert's "test.foo"38733* OpenSSL verify result: 1338734* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38735* closing connection #038736curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38737More details here: https://curl.se/docs/sslcerts.html3873838739curl failed to verify the legitimacy of the server and therefore could not38740establish a secure connection to it. To learn more about this situation and38741how to fix it, please visit the webpage mentioned above.38742* Host test.foo:443 was resolved.38743* IPv6: 2001:db8:1::338744* IPv4: 192.168.1.338745* Trying [2001:db8:1::3]:443...38746* ALPN: curl offers h2,http/1.138747} [5 bytes data]38748* TLSv1.3 (OUT), TLS handshake, Client hello (1):38749} [1552 bytes data]38750* SSL Trust Anchors:38751* OpenSSL default paths (fallback)38752{ [5 bytes data]38753* TLSv1.3 (IN), TLS handshake, Server hello (2):38754{ [1210 bytes data]38755* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38756{ [1 bytes data]38757* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38758{ [19 bytes data]38759* TLSv1.3 (IN), TLS handshake, Certificate (11):38760{ [1010 bytes data]38761* TLSv1.3 (IN), TLS handshake, CERT verify (15):38762{ [111 bytes data]38763* TLSv1.3 (IN), TLS handshake, Finished (20):38764{ [52 bytes data]38765* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38766} [1 bytes data]38767* TLSv1.3 (OUT), TLS handshake, Finished (20):38768} [52 bytes data]38769* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38770* ALPN: server accepted h238771* Server certificate:38772* subject: CN=test.foo38773* start date: Sep 20 15:17:16 2026 GMT38774* expire date: Oct 20 15:17:16 2028 GMT38775* issuer: CN=minica root ca 10ef5838776* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438777* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438778* subjectAltName: "test.foo" matches cert's "test.foo"38779* OpenSSL verify result: 1338780* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38781* closing connection #038782curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38783More details here: https://curl.se/docs/sslcerts.html3878438785curl failed to verify the legitimacy of the server and therefore could not38786establish a secure connection to it. To learn more about this situation and38787how to fix it, please visit the webpage mentioned above.38788* Trying [2001:db8:1::3]:443...38789* Host test.foo:443 was resolved.38790* IPv6: 2001:db8:1::338791* IPv4: 192.168.1.338792* ALPN: curl offers h2,http/1.138793} [5 bytes data]38794* TLSv1.3 (OUT), TLS handshake, Client hello (1):38795} [1552 bytes data]38796* SSL Trust Anchors:38797* OpenSSL default paths (fallback)38798{ [5 bytes data]38799* TLSv1.3 (IN), TLS handshake, Server hello (2):38800{ [1210 bytes data]38801* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38802{ [1 bytes data]38803* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38804{ [19 bytes data]38805* TLSv1.3 (IN), TLS handshake, Certificate (11):38806{ [1010 bytes data]38807* TLSv1.3 (IN), TLS handshake, CERT verify (15):38808{ [111 bytes data]38809* TLSv1.3 (IN), TLS handshake, Finished (20):38810{ [52 bytes data]38811* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38812} [1 bytes data]38813* TLSv1.3 (OUT), TLS handshake, Finished (20):38814} [52 bytes data]38815* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38816* ALPN: server accepted h238817* Server certificate:38818* subject: CN=test.foo38819* start date: Sep 20 15:17:16 2026 GMT38820* expire date: Oct 20 15:17:16 2028 GMT38821* issuer: CN=minica root ca 10ef5838822* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438823* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438824* subjectAltName: "test.foo" matches cert's "test.foo"38825* OpenSSL verify result: 1338826* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38827* closing connection #038828curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38829More details here: https://curl.se/docs/sslcerts.html3883038831curl failed to verify the legitimacy of the server and therefore could not38832establish a secure connection to it. To learn more about this situation and38833how to fix it, please visit the webpage mentioned above.38834* Host test.foo:443 was resolved.38835* IPv6: 2001:db8:1::338836* IPv4: 192.168.1.338837* Trying [2001:db8:1::3]:443...38838* ALPN: curl offers h2,http/1.138839} [5 bytes data]38840* TLSv1.3 (OUT), TLS handshake, Client hello (1):38841} [1552 bytes data]38842* SSL Trust Anchors:38843* OpenSSL default paths (fallback)38844{ [5 bytes data]38845* TLSv1.3 (IN), TLS handshake, Server hello (2):38846{ [1210 bytes data]38847* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38848{ [1 bytes data]38849* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38850{ [19 bytes data]38851* TLSv1.3 (IN), TLS handshake, Certificate (11):38852{ [1010 bytes data]38853* TLSv1.3 (IN), TLS handshake, CERT verify (15):38854{ [111 bytes data]38855* TLSv1.3 (IN), TLS handshake, Finished (20):38856{ [52 bytes data]38857* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38858} [1 bytes data]38859* TLSv1.3 (OUT), TLS handshake, Finished (20):38860} [52 bytes data]38861* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38862* ALPN: server accepted h238863* Server certificate:38864* subject: CN=test.foo38865* start date: Sep 20 15:17:16 2026 GMT38866* expire date: Oct 20 15:17:16 2028 GMT38867* issuer: CN=minica root ca 10ef5838868* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438869* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438870* subjectAltName: "test.foo" matches cert's "test.foo"38871* OpenSSL verify result: 1338872* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38873* closing connection #038874curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38875More details here: https://curl.se/docs/sslcerts.html3887638877curl failed to verify the legitimacy of the server and therefore could not38878establish a secure connection to it. To learn more about this situation and38879how to fix it, please visit the webpage mentioned above.38880* Host test.foo:443 was resolved.38881* IPv6: 2001:db8:1::338882* IPv4: 192.168.1.338883* Trying [2001:db8:1::3]:443...38884* ALPN: curl offers h2,http/1.138885} [5 bytes data]38886* TLSv1.3 (OUT), TLS handshake, Client hello (1):38887} [1552 bytes data]38888* SSL Trust Anchors:38889* OpenSSL default paths (fallback)38890{ [5 bytes data]38891* TLSv1.3 (IN), TLS handshake, Server hello (2):38892{ [1210 bytes data]38893* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38894{ [1 bytes data]38895* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38896{ [19 bytes data]38897* TLSv1.3 (IN), TLS handshake, Certificate (11):38898{ [1010 bytes data]38899* TLSv1.3 (IN), TLS handshake, CERT verify (15):38900{ [112 bytes data]38901* TLSv1.3 (IN), TLS handshake, Finished (20):38902{ [52 bytes data]38903* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38904} [1 bytes data]38905* TLSv1.3 (OUT), TLS handshake, Finished (20):38906} [52 bytes data]38907* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38908* ALPN: server accepted h238909* Server certificate:38910* subject: CN=test.foo38911* start date: Sep 20 15:17:16 2026 GMT38912* expire date: Oct 20 15:17:16 2028 GMT38913* issuer: CN=minica root ca 10ef5838914* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438915* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438916* subjectAltName: "test.foo" matches cert's "test.foo"38917* OpenSSL verify result: 1338918* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38919* closing connection #038920curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38921More details here: https://curl.se/docs/sslcerts.html3892238923curl failed to verify the legitimacy of the server and therefore could not38924establish a secure connection to it. To learn more about this situation and38925how to fix it, please visit the webpage mentioned above.38926* Host test.foo:443 was resolved.38927* IPv6: 2001:db8:1::338928* IPv4: 192.168.1.338929* Trying [2001:db8:1::3]:443...38930* ALPN: curl offers h2,http/1.138931} [5 bytes data]38932* TLSv1.3 (OUT), TLS handshake, Client hello (1):38933} [1552 bytes data]38934* SSL Trust Anchors:38935* OpenSSL default paths (fallback)38936{ [5 bytes data]38937* TLSv1.3 (IN), TLS handshake, Server hello (2):38938{ [1210 bytes data]38939* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38940{ [1 bytes data]38941* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38942{ [19 bytes data]38943* TLSv1.3 (IN), TLS handshake, Certificate (11):38944{ [1010 bytes data]38945* TLSv1.3 (IN), TLS handshake, CERT verify (15):38946{ [111 bytes data]38947* TLSv1.3 (IN), TLS handshake, Finished (20):38948{ [52 bytes data]38949* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38950} [1 bytes data]38951* TLSv1.3 (OUT), TLS handshake, Finished (20):38952} [52 bytes data]38953* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey38954* ALPN: server accepted h238955* Server certificate:38956* subject: CN=test.foo38957* start date: Sep 20 15:17:16 2026 GMT38958* expire date: Oct 20 15:17:16 2028 GMT38959* issuer: CN=minica root ca 10ef5838960* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438961* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38438962* subjectAltName: "test.foo" matches cert's "test.foo"38963* OpenSSL verify result: 1338964* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38965* closing connection #038966curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)38967More details here: https://curl.se/docs/sslcerts.html3896838969curl failed to verify the legitimacy of the server and therefore could not38970establish a secure connection to it. To learn more about this situation and38971how to fix it, please visit the webpage mentioned above.38972* Host test.foo:443 was resolved.38973* IPv6: 2001:db8:1::338974* IPv4: 192.168.1.338975* Trying [2001:db8:1::3]:443...38976* ALPN: curl offers h2,http/1.138977} [5 bytes data]38978* TLSv1.3 (OUT), TLS handshake, Client hello (1):38979} [1552 bytes data]38980* SSL Trust Anchors:38981* OpenSSL default paths (fallback)38982{ [5 bytes data]38983* TLSv1.3 (IN), TLS handshake, Server hello (2):38984{ [1210 bytes data]38985* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):38986{ [1 bytes data]38987* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):38988{ [19 bytes data]38989* TLSv1.3 (IN), TLS handshake, Certificate (11):38990{ [1010 bytes data]38991* TLSv1.3 (IN), TLS handshake, CERT verify (15):38992{ [111 bytes data]38993* TLSv1.3 (IN), TLS handshake, Finished (20):38994{ [52 bytes data]38995* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):38996} [1 bytes data]38997* TLSv1.3 (OUT), TLS handshake, Finished (20):38998} [52 bytes data]38999* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39000* ALPN: server accepted h239001* Server certificate:39002* subject: CN=test.foo39003* start date: Sep 20 15:17:16 2026 GMT39004* expire date: Oct 20 15:17:16 2028 GMT39005* issuer: CN=minica root ca 10ef5839006* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439007* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439008* subjectAltName: "test.foo" matches cert's "test.foo"39009* OpenSSL verify result: 1339010* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39011* closing connection #039012curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39013More details here: https://curl.se/docs/sslcerts.html3901439015curl failed to verify the legitimacy of the server and therefore could not39016establish a secure connection to it. To learn more about this situation and39017how to fix it, please visit the webpage mentioned above.39018* Host test.foo:443 was resolved.39019* IPv6: 2001:db8:1::339020* IPv4: 192.168.1.339021* Trying [2001:db8:1::3]:443...39022* ALPN: curl offers h2,http/1.139023} [5 bytes data]39024* TLSv1.3 (OUT), TLS handshake, Client hello (1):39025} [1552 bytes data]39026* SSL Trust Anchors:39027* OpenSSL default paths (fallback)39028{ [5 bytes data]39029* TLSv1.3 (IN), TLS handshake, Server hello (2):39030{ [1210 bytes data]39031* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39032{ [1 bytes data]39033* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39034{ [19 bytes data]39035* TLSv1.3 (IN), TLS handshake, Certificate (11):39036{ [1010 bytes data]39037* TLSv1.3 (IN), TLS handshake, CERT verify (15):39038{ [110 bytes data]39039* TLSv1.3 (IN), TLS handshake, Finished (20):39040{ [52 bytes data]39041* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39042} [1 bytes data]39043* TLSv1.3 (OUT), TLS handshake, Finished (20):39044} [52 bytes data]39045* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39046* ALPN: server accepted h239047* Server certificate:39048* subject: CN=test.foo39049* start date: Sep 20 15:17:16 2026 GMT39050* expire date: Oct 20 15:17:16 2028 GMT39051* issuer: CN=minica root ca 10ef5839052* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439053* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439054* subjectAltName: "test.foo" matches cert's "test.foo"39055* OpenSSL verify result: 1339056* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39057* closing connection #039058curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39059More details here: https://curl.se/docs/sslcerts.html3906039061curl failed to verify the legitimacy of the server and therefore could not39062establish a secure connection to it. To learn more about this situation and39063how to fix it, please visit the webpage mentioned above.39064* Host test.foo:443 was resolved.39065* IPv6: 2001:db8:1::339066* IPv4: 192.168.1.339067* Trying [2001:db8:1::3]:443...39068* ALPN: curl offers h2,http/1.139069} [5 bytes data]39070* TLSv1.3 (OUT), TLS handshake, Client hello (1):39071} [1552 bytes data]39072* SSL Trust Anchors:39073* OpenSSL default paths (fallback)39074{ [5 bytes data]39075* TLSv1.3 (IN), TLS handshake, Server hello (2):39076{ [1210 bytes data]39077* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39078{ [1 bytes data]39079* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39080{ [19 bytes data]39081* TLSv1.3 (IN), TLS handshake, Certificate (11):39082{ [1010 bytes data]39083* TLSv1.3 (IN), TLS handshake, CERT verify (15):39084{ [112 bytes data]39085* TLSv1.3 (IN), TLS handshake, Finished (20):39086{ [52 bytes data]39087* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39088} [1 bytes data]39089* TLSv1.3 (OUT), TLS handshake, Finished (20):39090} [52 bytes data]39091* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39092* ALPN: server accepted h239093* Server certificate:39094* subject: CN=test.foo39095* start date: Sep 20 15:17:16 2026 GMT39096* expire date: Oct 20 15:17:16 2028 GMT39097* issuer: CN=minica root ca 10ef5839098* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439099* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439100* subjectAltName: "test.foo" matches cert's "test.foo"39101* OpenSSL verify result: 1339102* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39103* closing connection #039104curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39105More details here: https://curl.se/docs/sslcerts.html3910639107curl failed to verify the legitimacy of the server and therefore could not39108establish a secure connection to it. To learn more about this situation and39109how to fix it, please visit the webpage mentioned above.39110* Trying [2001:db8:1::3]:443...39111* Host test.foo:443 was resolved.39112* IPv6: 2001:db8:1::339113* IPv4: 192.168.1.339114* ALPN: curl offers h2,http/1.139115} [5 bytes data]39116* TLSv1.3 (OUT), TLS handshake, Client hello (1):39117} [1552 bytes data]39118* SSL Trust Anchors:39119* OpenSSL default paths (fallback)39120{ [5 bytes data]39121* TLSv1.3 (IN), TLS handshake, Server hello (2):39122{ [1210 bytes data]39123* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39124{ [1 bytes data]39125* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39126{ [19 bytes data]39127* TLSv1.3 (IN), TLS handshake, Certificate (11):39128{ [1010 bytes data]39129* TLSv1.3 (IN), TLS handshake, CERT verify (15):39130{ [112 bytes data]39131* TLSv1.3 (IN), TLS handshake, Finished (20):39132{ [52 bytes data]39133* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39134} [1 bytes data]39135* TLSv1.3 (OUT), TLS handshake, Finished (20):39136} [52 bytes data]39137* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39138* ALPN: server accepted h239139* Server certificate:39140* subject: CN=test.foo39141* start date: Sep 20 15:17:16 2026 GMT39142* expire date: Oct 20 15:17:16 2028 GMT39143* issuer: CN=minica root ca 10ef5839144* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439145* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439146* subjectAltName: "test.foo" matches cert's "test.foo"39147* OpenSSL verify result: 1339148* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39149* closing connection #039150curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39151More details here: https://curl.se/docs/sslcerts.html3915239153curl failed to verify the legitimacy of the server and therefore could not39154establish a secure connection to it. To learn more about this situation and39155how to fix it, please visit the webpage mentioned above.39156* Host test.foo:443 was resolved.39157* IPv6: 2001:db8:1::339158* IPv4: 192.168.1.339159* Trying [2001:db8:1::3]:443...39160* ALPN: curl offers h2,http/1.139161} [5 bytes data]39162* TLSv1.3 (OUT), TLS handshake, Client hello (1):39163} [1552 bytes data]39164* SSL Trust Anchors:39165* OpenSSL default paths (fallback)39166{ [5 bytes data]39167* TLSv1.3 (IN), TLS handshake, Server hello (2):39168{ [1210 bytes data]39169* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39170{ [1 bytes data]39171* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39172{ [19 bytes data]39173* TLSv1.3 (IN), TLS handshake, Certificate (11):39174{ [1010 bytes data]39175* TLSv1.3 (IN), TLS handshake, CERT verify (15):39176{ [111 bytes data]39177* TLSv1.3 (IN), TLS handshake, Finished (20):39178{ [52 bytes data]39179* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39180} [1 bytes data]39181* TLSv1.3 (OUT), TLS handshake, Finished (20):39182} [52 bytes data]39183* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39184* ALPN: server accepted h239185* Server certificate:39186* subject: CN=test.foo39187* start date: Sep 20 15:17:16 2026 GMT39188* expire date: Oct 20 15:17:16 2028 GMT39189* issuer: CN=minica root ca 10ef5839190* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439191* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439192* subjectAltName: "test.foo" matches cert's "test.foo"39193* OpenSSL verify result: 1339194* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39195* closing connection #039196curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39197More details here: https://curl.se/docs/sslcerts.html3919839199curl failed to verify the legitimacy of the server and therefore could not39200establish a secure connection to it. To learn more about this situation and39201how to fix it, please visit the webpage mentioned above.39202* Host test.foo:443 was resolved.39203* IPv6: 2001:db8:1::339204* IPv4: 192.168.1.339205* Trying [2001:db8:1::3]:443...39206* ALPN: curl offers h2,http/1.139207} [5 bytes data]39208* TLSv1.3 (OUT), TLS handshake, Client hello (1):39209} [1552 bytes data]39210* SSL Trust Anchors:39211* OpenSSL default paths (fallback)39212{ [5 bytes data]39213* TLSv1.3 (IN), TLS handshake, Server hello (2):39214{ [1210 bytes data]39215* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39216{ [1 bytes data]39217* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39218{ [19 bytes data]39219* TLSv1.3 (IN), TLS handshake, Certificate (11):39220{ [1010 bytes data]39221* TLSv1.3 (IN), TLS handshake, CERT verify (15):39222{ [111 bytes data]39223* TLSv1.3 (IN), TLS handshake, Finished (20):39224{ [52 bytes data]39225* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39226} [1 bytes data]39227* TLSv1.3 (OUT), TLS handshake, Finished (20):39228} [52 bytes data]39229* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39230* ALPN: server accepted h239231* Server certificate:39232* subject: CN=test.foo39233* start date: Sep 20 15:17:16 2026 GMT39234* expire date: Oct 20 15:17:16 2028 GMT39235* issuer: CN=minica root ca 10ef5839236* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439237* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439238* subjectAltName: "test.foo" matches cert's "test.foo"39239* OpenSSL verify result: 1339240* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39241* closing connection #039242curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39243More details here: https://curl.se/docs/sslcerts.html3924439245curl failed to verify the legitimacy of the server and therefore could not39246establish a secure connection to it. To learn more about this situation and39247how to fix it, please visit the webpage mentioned above.39248* Host test.foo:443 was resolved.39249* IPv6: 2001:db8:1::339250* IPv4: 192.168.1.339251* Trying [2001:db8:1::3]:443...39252* ALPN: curl offers h2,http/1.139253} [5 bytes data]39254* TLSv1.3 (OUT), TLS handshake, Client hello (1):39255} [1552 bytes data]39256* SSL Trust Anchors:39257* OpenSSL default paths (fallback)39258{ [5 bytes data]39259* TLSv1.3 (IN), TLS handshake, Server hello (2):39260{ [1210 bytes data]39261* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39262{ [1 bytes data]39263* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39264{ [19 bytes data]39265* TLSv1.3 (IN), TLS handshake, Certificate (11):39266{ [1010 bytes data]39267* TLSv1.3 (IN), TLS handshake, CERT verify (15):39268{ [111 bytes data]39269* TLSv1.3 (IN), TLS handshake, Finished (20):39270{ [52 bytes data]39271* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39272} [1 bytes data]39273* TLSv1.3 (OUT), TLS handshake, Finished (20):39274} [52 bytes data]39275* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39276* ALPN: server accepted h239277* Server certificate:39278* subject: CN=test.foo39279* start date: Sep 20 15:17:16 2026 GMT39280* expire date: Oct 20 15:17:16 2028 GMT39281* issuer: CN=minica root ca 10ef5839282* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439283* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439284* subjectAltName: "test.foo" matches cert's "test.foo"39285* OpenSSL verify result: 1339286* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39287* closing connection #039288curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39289More details here: https://curl.se/docs/sslcerts.html3929039291curl failed to verify the legitimacy of the server and therefore could not39292establish a secure connection to it. To learn more about this situation and39293how to fix it, please visit the webpage mentioned above.39294* Host test.foo:443 was resolved.39295* IPv6: 2001:db8:1::339296* IPv4: 192.168.1.339297* Trying [2001:db8:1::3]:443...39298* ALPN: curl offers h2,http/1.139299} [5 bytes data]39300* TLSv1.3 (OUT), TLS handshake, Client hello (1):39301} [1552 bytes data]39302* SSL Trust Anchors:39303* OpenSSL default paths (fallback)39304{ [5 bytes data]39305* TLSv1.3 (IN), TLS handshake, Server hello (2):39306{ [1210 bytes data]39307* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39308{ [1 bytes data]39309* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39310{ [19 bytes data]39311* TLSv1.3 (IN), TLS handshake, Certificate (11):39312{ [1010 bytes data]39313* TLSv1.3 (IN), TLS handshake, CERT verify (15):39314{ [111 bytes data]39315* TLSv1.3 (IN), TLS handshake, Finished (20):39316{ [52 bytes data]39317* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39318} [1 bytes data]39319* TLSv1.3 (OUT), TLS handshake, Finished (20):39320} [52 bytes data]39321* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39322* ALPN: server accepted h239323* Server certificate:39324* subject: CN=test.foo39325* start date: Sep 20 15:17:16 2026 GMT39326* expire date: Oct 20 15:17:16 2028 GMT39327* issuer: CN=minica root ca 10ef5839328* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439329* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439330* subjectAltName: "test.foo" matches cert's "test.foo"39331* OpenSSL verify result: 1339332* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39333* closing connection #039334curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39335More details here: https://curl.se/docs/sslcerts.html3933639337curl failed to verify the legitimacy of the server and therefore could not39338establish a secure connection to it. To learn more about this situation and39339how to fix it, please visit the webpage mentioned above.39340* Host test.foo:443 was resolved.39341* IPv6: 2001:db8:1::339342* IPv4: 192.168.1.339343* Trying [2001:db8:1::3]:443...39344* ALPN: curl offers h2,http/1.139345} [5 bytes data]39346* TLSv1.3 (OUT), TLS handshake, Client hello (1):39347} [1552 bytes data]39348* SSL Trust Anchors:39349* OpenSSL default paths (fallback)39350{ [5 bytes data]39351* TLSv1.3 (IN), TLS handshake, Server hello (2):39352{ [1210 bytes data]39353* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39354{ [1 bytes data]39355* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39356{ [19 bytes data]39357* TLSv1.3 (IN), TLS handshake, Certificate (11):39358{ [1010 bytes data]39359* TLSv1.3 (IN), TLS handshake, CERT verify (15):39360{ [110 bytes data]39361* TLSv1.3 (IN), TLS handshake, Finished (20):39362{ [52 bytes data]39363* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39364} [1 bytes data]39365* TLSv1.3 (OUT), TLS handshake, Finished (20):39366} [52 bytes data]39367* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39368* ALPN: server accepted h239369* Server certificate:39370* subject: CN=test.foo39371* start date: Sep 20 15:17:16 2026 GMT39372* expire date: Oct 20 15:17:16 2028 GMT39373* issuer: CN=minica root ca 10ef5839374* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439375* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439376* subjectAltName: "test.foo" matches cert's "test.foo"39377* OpenSSL verify result: 1339378* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39379* closing connection #039380curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39381More details here: https://curl.se/docs/sslcerts.html3938239383curl failed to verify the legitimacy of the server and therefore could not39384establish a secure connection to it. To learn more about this situation and39385how to fix it, please visit the webpage mentioned above.39386* Host test.foo:443 was resolved.39387* IPv6: 2001:db8:1::339388* IPv4: 192.168.1.339389* Trying [2001:db8:1::3]:443...39390* ALPN: curl offers h2,http/1.139391} [5 bytes data]39392* TLSv1.3 (OUT), TLS handshake, Client hello (1):39393} [1552 bytes data]39394* SSL Trust Anchors:39395* OpenSSL default paths (fallback)39396{ [5 bytes data]39397* TLSv1.3 (IN), TLS handshake, Server hello (2):39398{ [1210 bytes data]39399* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39400{ [1 bytes data]39401* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39402{ [19 bytes data]39403* TLSv1.3 (IN), TLS handshake, Certificate (11):39404{ [1010 bytes data]39405* TLSv1.3 (IN), TLS handshake, CERT verify (15):39406{ [110 bytes data]39407* TLSv1.3 (IN), TLS handshake, Finished (20):39408{ [52 bytes data]39409* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39410} [1 bytes data]39411* TLSv1.3 (OUT), TLS handshake, Finished (20):39412} [52 bytes data]39413* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39414* ALPN: server accepted h239415* Server certificate:39416* subject: CN=test.foo39417* start date: Sep 20 15:17:16 2026 GMT39418* expire date: Oct 20 15:17:16 2028 GMT39419* issuer: CN=minica root ca 10ef5839420* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439421* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439422* subjectAltName: "test.foo" matches cert's "test.foo"39423* OpenSSL verify result: 1339424* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39425* closing connection #039426curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39427More details here: https://curl.se/docs/sslcerts.html3942839429curl failed to verify the legitimacy of the server and therefore could not39430establish a secure connection to it. To learn more about this situation and39431how to fix it, please visit the webpage mentioned above.39432* Host test.foo:443 was resolved.39433* IPv6: 2001:db8:1::339434* IPv4: 192.168.1.339435* Trying [2001:db8:1::3]:443...39436* ALPN: curl offers h2,http/1.139437} [5 bytes data]39438* TLSv1.3 (OUT), TLS handshake, Client hello (1):39439} [1552 bytes data]39440* SSL Trust Anchors:39441* OpenSSL default paths (fallback)39442{ [5 bytes data]39443* TLSv1.3 (IN), TLS handshake, Server hello (2):39444{ [1210 bytes data]39445* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39446{ [1 bytes data]39447* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39448{ [19 bytes data]39449* TLSv1.3 (IN), TLS handshake, Certificate (11):39450{ [1010 bytes data]39451* TLSv1.3 (IN), TLS handshake, CERT verify (15):39452{ [110 bytes data]39453* TLSv1.3 (IN), TLS handshake, Finished (20):39454{ [52 bytes data]39455* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39456} [1 bytes data]39457* TLSv1.3 (OUT), TLS handshake, Finished (20):39458} [52 bytes data]39459* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39460* ALPN: server accepted h239461* Server certificate:39462* subject: CN=test.foo39463* start date: Sep 20 15:17:16 2026 GMT39464* expire date: Oct 20 15:17:16 2028 GMT39465* issuer: CN=minica root ca 10ef5839466* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439467* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439468* subjectAltName: "test.foo" matches cert's "test.foo"39469* OpenSSL verify result: 1339470* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39471* closing connection #039472curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39473More details here: https://curl.se/docs/sslcerts.html3947439475curl failed to verify the legitimacy of the server and therefore could not39476establish a secure connection to it. To learn more about this situation and39477how to fix it, please visit the webpage mentioned above.39478* Host test.foo:443 was resolved.39479* IPv6: 2001:db8:1::339480* IPv4: 192.168.1.339481* Trying [2001:db8:1::3]:443...39482* ALPN: curl offers h2,http/1.139483} [5 bytes data]39484* TLSv1.3 (OUT), TLS handshake, Client hello (1):39485} [1552 bytes data]39486* SSL Trust Anchors:39487* OpenSSL default paths (fallback)39488{ [5 bytes data]39489* TLSv1.3 (IN), TLS handshake, Server hello (2):39490{ [1210 bytes data]39491* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39492{ [1 bytes data]39493* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39494{ [19 bytes data]39495* TLSv1.3 (IN), TLS handshake, Certificate (11):39496{ [1010 bytes data]39497* TLSv1.3 (IN), TLS handshake, CERT verify (15):39498{ [111 bytes data]39499* TLSv1.3 (IN), TLS handshake, Finished (20):39500{ [52 bytes data]39501* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39502} [1 bytes data]39503* TLSv1.3 (OUT), TLS handshake, Finished (20):39504} [52 bytes data]39505* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39506* ALPN: server accepted h239507* Server certificate:39508* subject: CN=test.foo39509* start date: Sep 20 15:17:16 2026 GMT39510* expire date: Oct 20 15:17:16 2028 GMT39511* issuer: CN=minica root ca 10ef5839512* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439513* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439514* subjectAltName: "test.foo" matches cert's "test.foo"39515* OpenSSL verify result: 1339516* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39517* closing connection #039518curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39519More details here: https://curl.se/docs/sslcerts.html3952039521curl failed to verify the legitimacy of the server and therefore could not39522establish a secure connection to it. To learn more about this situation and39523how to fix it, please visit the webpage mentioned above.39524* Host test.foo:443 was resolved.39525* IPv6: 2001:db8:1::339526* IPv4: 192.168.1.339527* Trying [2001:db8:1::3]:443...39528* ALPN: curl offers h2,http/1.139529} [5 bytes data]39530* TLSv1.3 (OUT), TLS handshake, Client hello (1):39531} [1552 bytes data]39532* SSL Trust Anchors:39533* OpenSSL default paths (fallback)39534{ [5 bytes data]39535* TLSv1.3 (IN), TLS handshake, Server hello (2):39536{ [1210 bytes data]39537* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39538{ [1 bytes data]39539* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39540{ [19 bytes data]39541* TLSv1.3 (IN), TLS handshake, Certificate (11):39542{ [1010 bytes data]39543* TLSv1.3 (IN), TLS handshake, CERT verify (15):39544{ [111 bytes data]39545* TLSv1.3 (IN), TLS handshake, Finished (20):39546{ [52 bytes data]39547* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39548} [1 bytes data]39549* TLSv1.3 (OUT), TLS handshake, Finished (20):39550} [52 bytes data]39551* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39552* ALPN: server accepted h239553* Server certificate:39554* subject: CN=test.foo39555* start date: Sep 20 15:17:16 2026 GMT39556* expire date: Oct 20 15:17:16 2028 GMT39557* issuer: CN=minica root ca 10ef5839558* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439559* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439560* subjectAltName: "test.foo" matches cert's "test.foo"39561* OpenSSL verify result: 1339562* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39563* closing connection #039564curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39565More details here: https://curl.se/docs/sslcerts.html3956639567curl failed to verify the legitimacy of the server and therefore could not39568establish a secure connection to it. To learn more about this situation and39569how to fix it, please visit the webpage mentioned above.39570* Host test.foo:443 was resolved.39571* IPv6: 2001:db8:1::339572* IPv4: 192.168.1.339573* Trying [2001:db8:1::3]:443...39574* ALPN: curl offers h2,http/1.139575} [5 bytes data]39576* TLSv1.3 (OUT), TLS handshake, Client hello (1):39577} [1552 bytes data]39578* SSL Trust Anchors:39579* OpenSSL default paths (fallback)39580{ [5 bytes data]39581* TLSv1.3 (IN), TLS handshake, Server hello (2):39582{ [1210 bytes data]39583* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39584{ [1 bytes data]39585* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39586{ [19 bytes data]39587* TLSv1.3 (IN), TLS handshake, Certificate (11):39588{ [1010 bytes data]39589* TLSv1.3 (IN), TLS handshake, CERT verify (15):39590{ [110 bytes data]39591* TLSv1.3 (IN), TLS handshake, Finished (20):39592{ [52 bytes data]39593* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39594} [1 bytes data]39595* TLSv1.3 (OUT), TLS handshake, Finished (20):39596} [52 bytes data]39597* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39598* ALPN: server accepted h239599* Server certificate:39600* subject: CN=test.foo39601* start date: Sep 20 15:17:16 2026 GMT39602* expire date: Oct 20 15:17:16 2028 GMT39603* issuer: CN=minica root ca 10ef5839604* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439605* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439606* subjectAltName: "test.foo" matches cert's "test.foo"39607* OpenSSL verify result: 1339608* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39609* closing connection #039610curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39611More details here: https://curl.se/docs/sslcerts.html3961239613curl failed to verify the legitimacy of the server and therefore could not39614establish a secure connection to it. To learn more about this situation and39615how to fix it, please visit the webpage mentioned above.39616client # [1411516.136750] client systemd[1]: Starting Cleanup of Temporary Directories...39617client # [1411516.246847] client systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.39618client # [1411516.247301] client systemd[1]: Finished Cleanup of Temporary Directories.39619* Trying [2001:db8:1::3]:443...39620* Host test.foo:443 was resolved.39621* IPv6: 2001:db8:1::339622* IPv4: 192.168.1.339623* ALPN: curl offers h2,http/1.139624} [5 bytes data]39625* TLSv1.3 (OUT), TLS handshake, Client hello (1):39626} [1552 bytes data]39627* SSL Trust Anchors:39628* OpenSSL default paths (fallback)39629{ [5 bytes data]39630* TLSv1.3 (IN), TLS handshake, Server hello (2):39631{ [1210 bytes data]39632* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39633{ [1 bytes data]39634* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39635{ [19 bytes data]39636* TLSv1.3 (IN), TLS handshake, Certificate (11):39637{ [1010 bytes data]39638* TLSv1.3 (IN), TLS handshake, CERT verify (15):39639{ [111 bytes data]39640* TLSv1.3 (IN), TLS handshake, Finished (20):39641{ [52 bytes data]39642* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39643} [1 bytes data]39644* TLSv1.3 (OUT), TLS handshake, Finished (20):39645} [52 bytes data]39646* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39647* ALPN: server accepted h239648* Server certificate:39649* subject: CN=test.foo39650* start date: Sep 20 15:17:16 2026 GMT39651* expire date: Oct 20 15:17:16 2028 GMT39652* issuer: CN=minica root ca 10ef5839653* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439654* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439655* subjectAltName: "test.foo" matches cert's "test.foo"39656* OpenSSL verify result: 1339657* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39658* closing connection #039659curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39660More details here: https://curl.se/docs/sslcerts.html3966139662curl failed to verify the legitimacy of the server and therefore could not39663establish a secure connection to it. To learn more about this situation and39664how to fix it, please visit the webpage mentioned above.39665* Host test.foo:443 was resolved.39666* IPv6: 2001:db8:1::339667* IPv4: 192.168.1.339668* Trying [2001:db8:1::3]:443...39669* ALPN: curl offers h2,http/1.139670} [5 bytes data]39671* TLSv1.3 (OUT), TLS handshake, Client hello (1):39672} [1552 bytes data]39673* SSL Trust Anchors:39674* OpenSSL default paths (fallback)39675{ [5 bytes data]39676* TLSv1.3 (IN), TLS handshake, Server hello (2):39677{ [1210 bytes data]39678* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39679{ [1 bytes data]39680* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39681{ [19 bytes data]39682* TLSv1.3 (IN), TLS handshake, Certificate (11):39683{ [1010 bytes data]39684* TLSv1.3 (IN), TLS handshake, CERT verify (15):39685{ [111 bytes data]39686* TLSv1.3 (IN), TLS handshake, Finished (20):39687{ [52 bytes data]39688* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39689} [1 bytes data]39690* TLSv1.3 (OUT), TLS handshake, Finished (20):39691} [52 bytes data]39692* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39693* ALPN: server accepted h239694* Server certificate:39695* subject: CN=test.foo39696* start date: Sep 20 15:17:16 2026 GMT39697* expire date: Oct 20 15:17:16 2028 GMT39698* issuer: CN=minica root ca 10ef5839699* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439700* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439701* subjectAltName: "test.foo" matches cert's "test.foo"39702* OpenSSL verify result: 1339703* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39704* closing connection #039705curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39706More details here: https://curl.se/docs/sslcerts.html3970739708curl failed to verify the legitimacy of the server and therefore could not39709establish a secure connection to it. To learn more about this situation and39710how to fix it, please visit the webpage mentioned above.39711* Host test.foo:443 was resolved.39712* IPv6: 2001:db8:1::339713* IPv4: 192.168.1.339714* Trying [2001:db8:1::3]:443...39715* ALPN: curl offers h2,http/1.139716} [5 bytes data]39717* TLSv1.3 (OUT), TLS handshake, Client hello (1):39718} [1552 bytes data]39719* SSL Trust Anchors:39720* OpenSSL default paths (fallback)39721{ [5 bytes data]39722* TLSv1.3 (IN), TLS handshake, Server hello (2):39723{ [1210 bytes data]39724* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39725{ [1 bytes data]39726* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39727{ [19 bytes data]39728* TLSv1.3 (IN), TLS handshake, Certificate (11):39729{ [1010 bytes data]39730* TLSv1.3 (IN), TLS handshake, CERT verify (15):39731{ [111 bytes data]39732* TLSv1.3 (IN), TLS handshake, Finished (20):39733{ [52 bytes data]39734* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39735} [1 bytes data]39736* TLSv1.3 (OUT), TLS handshake, Finished (20):39737} [52 bytes data]39738* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39739* ALPN: server accepted h239740* Server certificate:39741* subject: CN=test.foo39742* start date: Sep 20 15:17:16 2026 GMT39743* expire date: Oct 20 15:17:16 2028 GMT39744* issuer: CN=minica root ca 10ef5839745* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439746* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439747* subjectAltName: "test.foo" matches cert's "test.foo"39748* OpenSSL verify result: 1339749* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39750* closing connection #039751curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39752More details here: https://curl.se/docs/sslcerts.html3975339754curl failed to verify the legitimacy of the server and therefore could not39755establish a secure connection to it. To learn more about this situation and39756how to fix it, please visit the webpage mentioned above.39757* Host test.foo:443 was resolved.39758* IPv6: 2001:db8:1::339759* IPv4: 192.168.1.339760* Trying [2001:db8:1::3]:443...39761* ALPN: curl offers h2,http/1.139762} [5 bytes data]39763* TLSv1.3 (OUT), TLS handshake, Client hello (1):39764} [1552 bytes data]39765* SSL Trust Anchors:39766* OpenSSL default paths (fallback)39767{ [5 bytes data]39768* TLSv1.3 (IN), TLS handshake, Server hello (2):39769{ [1210 bytes data]39770* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39771{ [1 bytes data]39772* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39773{ [19 bytes data]39774* TLSv1.3 (IN), TLS handshake, Certificate (11):39775{ [1010 bytes data]39776* TLSv1.3 (IN), TLS handshake, CERT verify (15):39777{ [112 bytes data]39778* TLSv1.3 (IN), TLS handshake, Finished (20):39779{ [52 bytes data]39780* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39781} [1 bytes data]39782* TLSv1.3 (OUT), TLS handshake, Finished (20):39783} [52 bytes data]39784* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39785* ALPN: server accepted h239786* Server certificate:39787* subject: CN=test.foo39788* start date: Sep 20 15:17:16 2026 GMT39789* expire date: Oct 20 15:17:16 2028 GMT39790* issuer: CN=minica root ca 10ef5839791* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439792* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439793* subjectAltName: "test.foo" matches cert's "test.foo"39794* OpenSSL verify result: 1339795* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39796* closing connection #039797curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39798More details here: https://curl.se/docs/sslcerts.html3979939800curl failed to verify the legitimacy of the server and therefore could not39801establish a secure connection to it. To learn more about this situation and39802how to fix it, please visit the webpage mentioned above.39803* Host test.foo:443 was resolved.39804* IPv6: 2001:db8:1::339805* IPv4: 192.168.1.339806* Trying [2001:db8:1::3]:443...39807* ALPN: curl offers h2,http/1.139808} [5 bytes data]39809* TLSv1.3 (OUT), TLS handshake, Client hello (1):39810} [1552 bytes data]39811* SSL Trust Anchors:39812* OpenSSL default paths (fallback)39813{ [5 bytes data]39814* TLSv1.3 (IN), TLS handshake, Server hello (2):39815{ [1210 bytes data]39816* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39817{ [1 bytes data]39818* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39819{ [19 bytes data]39820* TLSv1.3 (IN), TLS handshake, Certificate (11):39821{ [1010 bytes data]39822* TLSv1.3 (IN), TLS handshake, CERT verify (15):39823{ [112 bytes data]39824* TLSv1.3 (IN), TLS handshake, Finished (20):39825{ [52 bytes data]39826* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39827} [1 bytes data]39828* TLSv1.3 (OUT), TLS handshake, Finished (20):39829} [52 bytes data]39830* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39831* ALPN: server accepted h239832* Server certificate:39833* subject: CN=test.foo39834* start date: Sep 20 15:17:16 2026 GMT39835* expire date: Oct 20 15:17:16 2028 GMT39836* issuer: CN=minica root ca 10ef5839837* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439838* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439839* subjectAltName: "test.foo" matches cert's "test.foo"39840* OpenSSL verify result: 1339841* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39842* closing connection #039843curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39844More details here: https://curl.se/docs/sslcerts.html3984539846curl failed to verify the legitimacy of the server and therefore could not39847establish a secure connection to it. To learn more about this situation and39848how to fix it, please visit the webpage mentioned above.39849ca # [1411521.823228] ca systemd[1]: Starting Cleanup of Temporary Directories...39850ca # [1411521.940733] ca systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.39851ca # [1411521.941084] ca systemd[1]: Finished Cleanup of Temporary Directories.39852* Host test.foo:443 was resolved.39853* IPv6: 2001:db8:1::339854* IPv4: 192.168.1.339855* Trying [2001:db8:1::3]:443...39856* ALPN: curl offers h2,http/1.139857} [5 bytes data]39858* TLSv1.3 (OUT), TLS handshake, Client hello (1):39859} [1552 bytes data]39860* SSL Trust Anchors:39861server # [1411521.943003] server systemd[1]: Starting Cleanup of Temporary Directories...39862server # [1411522.064504] server systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.39863server # [1411522.064756] server systemd[1]: Finished Cleanup of Temporary Directories.39864* OpenSSL default paths (fallback)39865{ [5 bytes data]39866* TLSv1.3 (IN), TLS handshake, Server hello (2):39867{ [1210 bytes data]39868* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39869{ [1 bytes data]39870* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39871{ [19 bytes data]39872* TLSv1.3 (IN), TLS handshake, Certificate (11):39873{ [1010 bytes data]39874* TLSv1.3 (IN), TLS handshake, CERT verify (15):39875{ [110 bytes data]39876* TLSv1.3 (IN), TLS handshake, Finished (20):39877{ [52 bytes data]39878* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39879} [1 bytes data]39880* TLSv1.3 (OUT), TLS handshake, Finished (20):39881} [52 bytes data]39882* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39883* ALPN: server accepted h239884* Server certificate:39885* subject: CN=test.foo39886* start date: Sep 20 15:17:16 2026 GMT39887* expire date: Oct 20 15:17:16 2028 GMT39888* issuer: CN=minica root ca 10ef5839889* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439890* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439891* subjectAltName: "test.foo" matches cert's "test.foo"39892* OpenSSL verify result: 1339893* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39894* closing connection #039895curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39896More details here: https://curl.se/docs/sslcerts.html3989739898curl failed to verify the legitimacy of the server and therefore could not39899establish a secure connection to it. To learn more about this situation and39900how to fix it, please visit the webpage mentioned above.39901* Host test.foo:443 was resolved.39902* IPv6: 2001:db8:1::339903* IPv4: 192.168.1.339904* Trying [2001:db8:1::3]:443...39905* ALPN: curl offers h2,http/1.139906} [5 bytes data]39907* TLSv1.3 (OUT), TLS handshake, Client hello (1):39908} [1552 bytes data]39909* SSL Trust Anchors:39910* OpenSSL default paths (fallback)39911{ [5 bytes data]39912* TLSv1.3 (IN), TLS handshake, Server hello (2):39913{ [1210 bytes data]39914* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39915{ [1 bytes data]39916* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39917{ [19 bytes data]39918* TLSv1.3 (IN), TLS handshake, Certificate (11):39919{ [1010 bytes data]39920* TLSv1.3 (IN), TLS handshake, CERT verify (15):39921{ [111 bytes data]39922* TLSv1.3 (IN), TLS handshake, Finished (20):39923{ [52 bytes data]39924* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39925} [1 bytes data]39926* TLSv1.3 (OUT), TLS handshake, Finished (20):39927} [52 bytes data]39928* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39929* ALPN: server accepted h239930* Server certificate:39931* subject: CN=test.foo39932* start date: Sep 20 15:17:16 2026 GMT39933* expire date: Oct 20 15:17:16 2028 GMT39934* issuer: CN=minica root ca 10ef5839935* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439936* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439937* subjectAltName: "test.foo" matches cert's "test.foo"39938* OpenSSL verify result: 1339939* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39940* closing connection #039941curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39942More details here: https://curl.se/docs/sslcerts.html3994339944curl failed to verify the legitimacy of the server and therefore could not39945establish a secure connection to it. To learn more about this situation and39946how to fix it, please visit the webpage mentioned above.39947* Host test.foo:443 was resolved.39948* IPv6: 2001:db8:1::339949* IPv4: 192.168.1.339950* Trying [2001:db8:1::3]:443...39951* ALPN: curl offers h2,http/1.139952} [5 bytes data]39953* TLSv1.3 (OUT), TLS handshake, Client hello (1):39954} [1552 bytes data]39955* SSL Trust Anchors:39956* OpenSSL default paths (fallback)39957{ [5 bytes data]39958* TLSv1.3 (IN), TLS handshake, Server hello (2):39959{ [1210 bytes data]39960* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):39961{ [1 bytes data]39962* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):39963{ [19 bytes data]39964* TLSv1.3 (IN), TLS handshake, Certificate (11):39965{ [1010 bytes data]39966* TLSv1.3 (IN), TLS handshake, CERT verify (15):39967{ [111 bytes data]39968* TLSv1.3 (IN), TLS handshake, Finished (20):39969{ [52 bytes data]39970* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):39971} [1 bytes data]39972* TLSv1.3 (OUT), TLS handshake, Finished (20):39973} [52 bytes data]39974* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey39975* ALPN: server accepted h239976* Server certificate:39977* subject: CN=test.foo39978* start date: Sep 20 15:17:16 2026 GMT39979* expire date: Oct 20 15:17:16 2028 GMT39980* issuer: CN=minica root ca 10ef5839981* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439982* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38439983* subjectAltName: "test.foo" matches cert's "test.foo"39984* OpenSSL verify result: 1339985* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39986* closing connection #039987curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)39988More details here: https://curl.se/docs/sslcerts.html3998939990curl failed to verify the legitimacy of the server and therefore could not39991establish a secure connection to it. To learn more about this situation and39992how to fix it, please visit the webpage mentioned above.39993* Host test.foo:443 was resolved.39994* IPv6: 2001:db8:1::339995* IPv4: 192.168.1.339996* Trying [2001:db8:1::3]:443...39997* ALPN: curl offers h2,http/1.139998} [5 bytes data]39999* TLSv1.3 (OUT), TLS handshake, Client hello (1):40000} [1552 bytes data]40001* SSL Trust Anchors:40002* OpenSSL default paths (fallback)40003{ [5 bytes data]40004* TLSv1.3 (IN), TLS handshake, Server hello (2):40005{ [1210 bytes data]40006* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):40007{ [1 bytes data]40008* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):40009{ [19 bytes data]40010* TLSv1.3 (IN), TLS handshake, Certificate (11):40011{ [1010 bytes data]40012* TLSv1.3 (IN), TLS handshake, CERT verify (15):40013{ [111 bytes data]40014* TLSv1.3 (IN), TLS handshake, Finished (20):40015{ [52 bytes data]40016* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):40017} [1 bytes data]40018* TLSv1.3 (OUT), TLS handshake, Finished (20):40019} [52 bytes data]40020* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey40021* ALPN: server accepted h240022* Server certificate:40023* subject: CN=test.foo40024* start date: Sep 20 15:17:16 2026 GMT40025* expire date: Oct 20 15:17:16 2028 GMT40026* issuer: CN=minica root ca 10ef5840027* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38440028* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38440029* subjectAltName: "test.foo" matches cert's "test.foo"40030* OpenSSL verify result: 1340031* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)40032* closing connection #040033curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)40034More details here: https://curl.se/docs/sslcerts.html4003540036curl failed to verify the legitimacy of the server and therefore could not40037establish a secure connection to it. To learn more about this situation and40038how to fix it, please visit the webpage mentioned above.40039* Host test.foo:443 was resolved.40040* IPv6: 2001:db8:1::340041* IPv4: 192.168.1.340042* Trying [2001:db8:1::3]:443...40043* ALPN: curl offers h2,http/1.140044} [5 bytes data]40045* TLSv1.3 (OUT), TLS handshake, Client hello (1):40046} [1552 bytes data]40047* SSL Trust Anchors:40048* OpenSSL default paths (fallback)40049{ [5 bytes data]40050* TLSv1.3 (IN), TLS handshake, Server hello (2):40051{ [1210 bytes data]40052* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):40053{ [1 bytes data]40054* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):40055{ [19 bytes data]40056* TLSv1.3 (IN), TLS handshake, Certificate (11):40057{ [1010 bytes data]40058* TLSv1.3 (IN), TLS handshake, CERT verify (15):40059{ [110 bytes data]40060* TLSv1.3 (IN), TLS handshake, Finished (20):40061{ [52 bytes data]40062* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):40063} [1 bytes data]40064* TLSv1.3 (OUT), TLS handshake, Finished (20):40065} [52 bytes data]40066* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey40067* ALPN: server accepted h240068* Server certificate:40069* subject: CN=test.foo40070* start date: Sep 20 15:17:16 2026 GMT40071* expire date: Oct 20 15:17:16 2028 GMT40072* issuer: CN=minica root ca 10ef5840073* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38440074* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA38440075* subjectAltName: "test.foo" matches cert's "test.foo"40076* OpenSSL verify result: 1340077* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)40078* closing connection #040079curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)40080More details here: https://curl.se/docs/sslcerts.html4008140082curl failed to verify the legitimacy of the server and therefore could not40083establish a secure connection to it. To learn more about this situation and40084how to fix it, please visit the webpage mentioned above.40085!!! Traceback (most recent call last):40086!!! File "<string>", line 13, in <module>40087!!! client.wait_until_succeeds("curl -v https://test.foo")40088!!! 40089!!! RequestedAssertionFailed: action timed out after 900.20 seconds (timeout=900.0)40090cleanup40091kill NspawnMachine (pid 53)40092kill NspawnMachine (pid 54)40093Container ca terminated by signal KILL.40094kill NspawnMachine (pid 55)40095Container client terminated by signal KILL.40096Container server terminated by signal KILL.40097(finished: cleanup, in 0.49 seconds)