Is the Let's encrypt certificate is not good enough for Sakia?

[me@Main-Computer sakia]$ sakia -d --currency=Guilder-Test
[11646] PyInstaller Bootloader 3.x
[11646] LOADER: executable is /opt/sakia/sakia.bin
[11646] LOADER: homepath is /opt/sakia
[11646] LOADER: _MEIPASS2 is NULL
[11646] LOADER: archivename is /opt/sakia/sakia.bin
[11646] LOADER: Extracting binaries
[11646] LOADER: Executing self as child
[11646] LOADER: set _MEIPASS2 to /opt/sakia
[11646] LOADER: LD_LIBRARY_PATH=/opt/sakia
[11647] PyInstaller Bootloader 3.x
[11647] LOADER: executable is /opt/sakia/sakia.bin
[11647] LOADER: homepath is /opt/sakia
[11647] LOADER: _MEIPASS2 is /opt/sakia
[11647] LOADER: archivename is /opt/sakia/sakia.bin
[11647] LOADER: Already in the child - running user's code.
[11647] LOADER: Python library: /opt/sakia/libpython3.5m.so.1.0
[11647] LOADER: Loaded functions from Python library.
[11647] LOADER: Manipulating environment (sys.path, sys.prefix)
[11647] LOADER: Pre-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
[11647] LOADER: sys.prefix is /opt/sakia
[11647] LOADER: Setting runtime options
[11647] LOADER: Initializing python
[11647] LOADER: Overriding Python's sys.path
[11647] LOADER: Post-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
[11647] LOADER: Setting sys.argv
[11647] LOADER: setting sys._MEIPASS
[11647] LOADER: importing modules from CArchive
[11647] LOADER: extracted struct
[11647] LOADER: callfunction returned...
[11647] LOADER: extracted pyimod01_os_path
[11647] LOADER: callfunction returned...
[11647] LOADER: extracted pyimod02_archive
[11647] LOADER: callfunction returned...
[11647] LOADER: extracted pyimod03_importers
[11647] LOADER: callfunction returned...
[11647] LOADER: Installing PYZ archive with Python modules.
[11647] LOADER: PYZ archive: out00-PYZ.pyz
[11647] LOADER: Running pyiboot01_bootstrap.py
[11647] LOADER: Running pyi_rth_qt5.py
[11647] LOADER: Running pyi_rth_multiprocessing.py
[11647] LOADER: Running pyi_rth_pkgres.py
[11647] LOADER: Running main.py
DEBUG:meta:prepare:Initializing meta database
DEBUG:meta:upgrade_database:Begin upgrade of database...
DEBUG:meta:upgrade_database:Upgrading to version 0...
DEBUG:meta:create_all_tables:Initialiazing all databases
DEBUG:meta:upgrade_database:Upgrading to version 1...
DEBUG:meta:add_ud_rythm_parameters:Add ud rythm parameters to blockchains table
DEBUG:meta:upgrade_database:Upgrading to version 2...
DEBUG:meta:add_contacts:Add contacts table
DEBUG:meta:upgrade_database:Upgrading to version 3...
DEBUG:meta:add_sentry_property:Add sentry property
DEBUG:meta:upgrade_database:Upgrading to version 4...
DEBUG:meta:add_last_state_change_property:Add last state change property
DEBUG:meta:upgrade_database:Upgrading to version 5...
DEBUG:meta:refactor_transactions:Refactor transactions
DEBUG:meta:upgrade_database:End upgrade of database...
DEBUG:network:add_connector:AbE4R connected
DEBUG:blockchain:initialize_blockchain:Requesting blockchain parameters
DEBUG:bma:verified_get:Requesting parameters on endpoint BMAS duniter-folatt.nohost.me 443
DEBUG:node:connect_current_block:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)] : AbE4R
DEBUG:node:change_state_and_emit:[AbE4R] Changing state 1 > 2
DEBUG:node:safe_request:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
DEBUG:node:request_peers:[AbE4R] Could not connect to any BMA endpoint
DEBUG:node:connect_peers:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
DEBUG:bma:verified_get:Exception in responses : Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
DEBUG:node:connect_current_block:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)] : AbE4R
DEBUG:node:connect_peers:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
DEBUG:node:connect_current_block:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)] : AbE4R
DEBUG:node:connect_peers:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
DEBUG:node:connect_current_block:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)] : AbE4R
DEBUG:node:connect_peers:[AbE4R] Cannot connect to host duniter-folatt.nohost.me:443 ssl:True [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)]
Error connecting to the network : Error : No peer answered in  community (1 peers available)

I’m confused if this means Server B is found, or that Server A is found, which is not running Duniter. How can I verify this?

Problem solved. It was connecting to Server A.
Disabling ipv4 in duniter with duniter wizard network-reconfigure and setting remoteipv4 to None did the trick.