New hub not delivering posts
Hello everyone,
I would appreciate some help in de-bugging my hub to join the network.
My freshly set up hub does not seem to deliver posts and connection requests, and it does not display the public stream (in spite of the respective channel permission for diagnosis). I dug into the help's Admin guide and third-party how-tos, but no luck. I do not even really know what to look for. Appearently, I can receive posts from confirmed connections, though (tested with a channed on another hub). Subscribed RSS Feeds are delivered. A clone on a different hub of one channel is appearently linked, but there, I see the public stream of several thousend posts - But on my hub, I see only the subscribed RSS feeds. None of my 7 connection requests was responded to, I got responses from the cloned channel on another hub.
The hub is setup manually on a hosted webspace (netcup.eu). The admin guide talked about a Cron job ("see below") - but did not follow up on that. I remembered the Cron job from an attempt to join Hubzilla a year ago, so I (re-)searched and found on third party guides older manuals about a "master.php" Cron job executed every ten minutes, so I configured it (no errors).
Does anyone have a clue why my hub is not connecting properly, or what to look for? I would appreciate any help, thanks in advance!
In the Hubzilla log, I have several "[Error]" messages
Failes to connect to <XYZ> ; Connection refused,
Could not resolvehost: <XYZ>[: No route to host],
SSL: no alternative certificate subject name matches target host name '<XYZ>',
and many Infos with lines like
<...>LOG_INFO:<...>:network.php:197:z_fetch_url: z_fetch_url: error: http://<...>: Could not resolve host: hubzilla.x.hfrc.de
<...>:LOG_INFO:<...>:Finger.php:126:run: zot_finger: no results
<...>:LOG_INFO:<...>:network.php:385:z_post_url: z_post_url: error: https://<...>: Failed to connect to <...> port 443: Connection refused
