Hosting powered by RESTENA

Wordpress websites - FAQ

Wordpress is support on RESTENA hosting. In order to obtain smooth operation, please take care of the following constraints!

Outbound network access only possible with proxy

As webspace does not allow access to network resources without going through a filtering proxy, Wordpress will by default not be able to check for updates or even install them automatically.

To solve this restriction, please apply the following code to your wordpress configuration:

When connected you can ajust the proxy whitelist, both for HTTP targets (provide whole target URL) and HTTPS targets (provide target hostname).

In the proxy log the HTTPS targets are listed as 'CONNECT nom.du.site:443'.

Cron jobs

Wordpress has the ability to perform some tasks automatically based on time, such as scheduled publication of posts. In order to do so it calls back to itself via HTTP which gets blocked at server firewall.

In order to enable cron jobs you have multiple options:

• Define cron tasks over SSH that call Wordpress's wp-cron.php and in your wp-config.php add the following define:

  define('DISABLE_WP_CRON', true);

  Remember to add you main site ULR to the proxy white-list for this to work.

• Let wordpress perform the cron tasks after sending page content to visitors.

• Let wordpress perform the cron tasks through calls to itself, which requires to add the following to your theme's functions.php (create a child theme to avoid losing your changes on next theme update):

  add_filter('pre_http_send_through_proxy', 'always_use_proxy', 10, 4);
  
  function always_use_proxy() {
  return true;
  }

  Alternatively to functions.php file, under PHP-7.3 and above you can also force proxy usage by adding the following lines to your wp_config.php (after definition of the constants WP_PROXY_*):

  ini_set('curl.proxy', WP_PROXY_HOST.':'.WP_PROXY_PORT);
  ini_set('curl.proxyuserpwd', WP_PROXY_USERNAME.':'.WP_PROXY_PASSWORD);

  Remember to add you main site URL to the proxy white-list for this to work.

Pingpback

The pingback feature of WordPress is blocked by the server's firewall and will only be allowed the outbound proxy on a case by case decision.

Pingback requests from outside are partially blocked as they are used in abusice manner (distributed denial of service attack, DDOS). By default request with a WordPress UserAgent including "verifying pingback" string will get rejected with error code 403.