This notification is usually the result of too strict security settings (for example, by plugins such as Wordfence or Cloudflare, firewalls or your host) or a slow server and results in a server-side timeout. You can check your server and page speed at any time with the Google page speed test.
This behavior can also be caused by temporarily blocked outgoing connections from your website, for example, if you share too many posts with Blog2Social in a short period of time. Such blocks are often implemented by hosting providers as a security measure and while they are typically resolved automatically, they can sometimes cause interruptions in connectivity.
Besides that, there are several solutions for this request.
If you use an additional Firewall like Wordfence or Cloudflare, please make sure that your settings allow outgoing connections or include an exception for Blog2Social.
You could also try whitelisting Blog2Social since proper access could be blocked by installed security plugins or additional firewalls on the server-side as well. If you are using security plugins or server sided settings please try to whitelist your own server IP as well in order to allow automatic curl processes if you face any issues. You may also try to unblock our IPs if required.
Server location: Germany
IPv4
178.77.85.168
IPv6
2a01:488:42:1000:b24d:55a8:ffb8:ccaf
Please make sure that your website meets the system requirements for Blog2Social.
If your hoster provides a server hosted caching and activated "nginx caching" it might result in a "connection to the server failed" message. This happens due to incorrect DNS settings on the part of the hoster, resulting in a 504 error-notification. Please contact your hoster in this case in order to solve the request.
Please change the max execution time in your .htaccess File (in the root folder of WordPress) to 40 or highger: "php_value max_execution_time 40"
You can also use the WordPress plugin "WP Maximum Execution Time exceeded" for this: https://wordpress.org/plugins/wp-maximum-execution-time-exceeded/
Tags: Connection failed, Connection is broken, Connection to the server failed