http error: curl error 7: failed to connect to wordpress.org port 80












1















I freshly installed an Ubuntu server 16.04 with LEMP and wordpress.
But it seems that I have missed a step in the process, as I have the following error on the websites.



http error: curl error 7: failed to connect to wordpress.org port 80.


The sites is working fine beside that it is configure in a virtual machine as I'm developing a website, first on my local machine to test everything in local.



Here is my config file:



server {
listen 80;
server_name 192.168.1.3; #ipaddress;
root /usr/share/nginx/mrupgrade.be/;
index index.php index.html index.htm;

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location = /50x.html {
root /usr/share/nginx/html;
}
location / {
try_files $uri $uri/ /index.php;
}

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location ~ .php$ {
try_files $uri = 404;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
root /usr/share/nginx/mrupgrade.be/;
}
}


Note that I have configured the firewall with those rules:



Thanks in advance for your help.



Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED


wp-config.php



<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the
* installation. You don't have to use the web site, you can
* copy this file to "wp-config.php" and fill in the values.
*
* This file contains the following configurations:
*
* * MySQL settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://codex.wordpress.org/Editing_wp-config.php
*
* @package WordPress
*/

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'mysite_wp_db');

/** MySQL database username */
define('DB_USER', 'mysite_user');

/** MySQL database password */
define('DB_PASSWORD', 'mysite');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each
* a unique prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');


/var/www/mrupgrade.be/public_html the site location that's nginx site config



user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
worker_connections 768;
# multi_accept on;
}

http {

##
# Basic Settings
##

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;

# server_names_hash_bucket_size 64;
# server_name_in_redirect off;

include /etc/nginx/mime.types;
default_type application/octet-stream;

##
# SSL Settings
##

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;

##
# Logging Settings
##

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

##
# Gzip Settings
##

gzip on;
gzip_disable "msie6";

# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

##
# Virtual Host Configs
##

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}


My /etc/nginx/nginx.conf



#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}


So in image everything is fine expect some stuff maybe a lib is missing or I don't know I installed fpm fast cgi.



The wordpress Can't connect to the web eith http request.



RSS flux error



I don't really know what it could be any clue would be welcome.



Thanks in advance for your help.










share|improve this question




















  • 2





    Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

    – muru
    Dec 28 '16 at 14:45








  • 2





    Please edit your post to include your (suitably redacted) wp-config.php

    – muru
    Dec 28 '16 at 14:47











  • The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

    – muru
    Dec 28 '16 at 15:35











  • Ok thanks I would change the rules now and see if it works.

    – Raphael Teubner
    Dec 28 '16 at 15:37
















1















I freshly installed an Ubuntu server 16.04 with LEMP and wordpress.
But it seems that I have missed a step in the process, as I have the following error on the websites.



http error: curl error 7: failed to connect to wordpress.org port 80.


The sites is working fine beside that it is configure in a virtual machine as I'm developing a website, first on my local machine to test everything in local.



Here is my config file:



server {
listen 80;
server_name 192.168.1.3; #ipaddress;
root /usr/share/nginx/mrupgrade.be/;
index index.php index.html index.htm;

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location = /50x.html {
root /usr/share/nginx/html;
}
location / {
try_files $uri $uri/ /index.php;
}

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location ~ .php$ {
try_files $uri = 404;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
root /usr/share/nginx/mrupgrade.be/;
}
}


Note that I have configured the firewall with those rules:



Thanks in advance for your help.



Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED


wp-config.php



<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the
* installation. You don't have to use the web site, you can
* copy this file to "wp-config.php" and fill in the values.
*
* This file contains the following configurations:
*
* * MySQL settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://codex.wordpress.org/Editing_wp-config.php
*
* @package WordPress
*/

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'mysite_wp_db');

/** MySQL database username */
define('DB_USER', 'mysite_user');

/** MySQL database password */
define('DB_PASSWORD', 'mysite');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each
* a unique prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');


/var/www/mrupgrade.be/public_html the site location that's nginx site config



user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
worker_connections 768;
# multi_accept on;
}

http {

##
# Basic Settings
##

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;

# server_names_hash_bucket_size 64;
# server_name_in_redirect off;

include /etc/nginx/mime.types;
default_type application/octet-stream;

##
# SSL Settings
##

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;

##
# Logging Settings
##

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

##
# Gzip Settings
##

gzip on;
gzip_disable "msie6";

# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

##
# Virtual Host Configs
##

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}


My /etc/nginx/nginx.conf



#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}


So in image everything is fine expect some stuff maybe a lib is missing or I don't know I installed fpm fast cgi.



The wordpress Can't connect to the web eith http request.



RSS flux error



I don't really know what it could be any clue would be welcome.



Thanks in advance for your help.










share|improve this question




















  • 2





    Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

    – muru
    Dec 28 '16 at 14:45








  • 2





    Please edit your post to include your (suitably redacted) wp-config.php

    – muru
    Dec 28 '16 at 14:47











  • The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

    – muru
    Dec 28 '16 at 15:35











  • Ok thanks I would change the rules now and see if it works.

    – Raphael Teubner
    Dec 28 '16 at 15:37














1












1








1








I freshly installed an Ubuntu server 16.04 with LEMP and wordpress.
But it seems that I have missed a step in the process, as I have the following error on the websites.



http error: curl error 7: failed to connect to wordpress.org port 80.


The sites is working fine beside that it is configure in a virtual machine as I'm developing a website, first on my local machine to test everything in local.



Here is my config file:



server {
listen 80;
server_name 192.168.1.3; #ipaddress;
root /usr/share/nginx/mrupgrade.be/;
index index.php index.html index.htm;

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location = /50x.html {
root /usr/share/nginx/html;
}
location / {
try_files $uri $uri/ /index.php;
}

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location ~ .php$ {
try_files $uri = 404;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
root /usr/share/nginx/mrupgrade.be/;
}
}


Note that I have configured the firewall with those rules:



Thanks in advance for your help.



Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED


wp-config.php



<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the
* installation. You don't have to use the web site, you can
* copy this file to "wp-config.php" and fill in the values.
*
* This file contains the following configurations:
*
* * MySQL settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://codex.wordpress.org/Editing_wp-config.php
*
* @package WordPress
*/

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'mysite_wp_db');

/** MySQL database username */
define('DB_USER', 'mysite_user');

/** MySQL database password */
define('DB_PASSWORD', 'mysite');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each
* a unique prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');


/var/www/mrupgrade.be/public_html the site location that's nginx site config



user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
worker_connections 768;
# multi_accept on;
}

http {

##
# Basic Settings
##

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;

# server_names_hash_bucket_size 64;
# server_name_in_redirect off;

include /etc/nginx/mime.types;
default_type application/octet-stream;

##
# SSL Settings
##

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;

##
# Logging Settings
##

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

##
# Gzip Settings
##

gzip on;
gzip_disable "msie6";

# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

##
# Virtual Host Configs
##

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}


My /etc/nginx/nginx.conf



#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}


So in image everything is fine expect some stuff maybe a lib is missing or I don't know I installed fpm fast cgi.



The wordpress Can't connect to the web eith http request.



RSS flux error



I don't really know what it could be any clue would be welcome.



Thanks in advance for your help.










share|improve this question
















I freshly installed an Ubuntu server 16.04 with LEMP and wordpress.
But it seems that I have missed a step in the process, as I have the following error on the websites.



http error: curl error 7: failed to connect to wordpress.org port 80.


The sites is working fine beside that it is configure in a virtual machine as I'm developing a website, first on my local machine to test everything in local.



Here is my config file:



server {
listen 80;
server_name 192.168.1.3; #ipaddress;
root /usr/share/nginx/mrupgrade.be/;
index index.php index.html index.htm;

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location = /50x.html {
root /usr/share/nginx/html;
}
location / {
try_files $uri $uri/ /index.php;
}

error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;

location ~ .php$ {
try_files $uri = 404;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
root /usr/share/nginx/mrupgrade.be/;
}
}


Note that I have configured the firewall with those rules:



Thanks in advance for your help.



Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED


wp-config.php



<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the
* installation. You don't have to use the web site, you can
* copy this file to "wp-config.php" and fill in the values.
*
* This file contains the following configurations:
*
* * MySQL settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://codex.wordpress.org/Editing_wp-config.php
*
* @package WordPress
*/

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'mysite_wp_db');

/** MySQL database username */
define('DB_USER', 'mysite_user');

/** MySQL database password */
define('DB_PASSWORD', 'mysite');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each
* a unique prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');


/var/www/mrupgrade.be/public_html the site location that's nginx site config



user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
worker_connections 768;
# multi_accept on;
}

http {

##
# Basic Settings
##

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;

# server_names_hash_bucket_size 64;
# server_name_in_redirect off;

include /etc/nginx/mime.types;
default_type application/octet-stream;

##
# SSL Settings
##

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;

##
# Logging Settings
##

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

##
# Gzip Settings
##

gzip on;
gzip_disable "msie6";

# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

##
# Virtual Host Configs
##

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}


My /etc/nginx/nginx.conf



#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}


So in image everything is fine expect some stuff maybe a lib is missing or I don't know I installed fpm fast cgi.



The wordpress Can't connect to the web eith http request.



RSS flux error



I don't really know what it could be any clue would be welcome.



Thanks in advance for your help.







server php nginx wordpress






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '16 at 15:31







Raphael Teubner

















asked Dec 28 '16 at 14:41









Raphael TeubnerRaphael Teubner

10614




10614








  • 2





    Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

    – muru
    Dec 28 '16 at 14:45








  • 2





    Please edit your post to include your (suitably redacted) wp-config.php

    – muru
    Dec 28 '16 at 14:47











  • The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

    – muru
    Dec 28 '16 at 15:35











  • Ok thanks I would change the rules now and see if it works.

    – Raphael Teubner
    Dec 28 '16 at 15:37














  • 2





    Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

    – muru
    Dec 28 '16 at 14:45








  • 2





    Please edit your post to include your (suitably redacted) wp-config.php

    – muru
    Dec 28 '16 at 14:47











  • The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

    – muru
    Dec 28 '16 at 15:35











  • Ok thanks I would change the rules now and see if it works.

    – Raphael Teubner
    Dec 28 '16 at 15:37








2




2





Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

– muru
Dec 28 '16 at 14:45







Why do you think connecting to wordpress.org will go to your local server? Oh, I see - that's not a curl command error, but a PHP error shown on your webpages.

– muru
Dec 28 '16 at 14:45






2




2





Please edit your post to include your (suitably redacted) wp-config.php

– muru
Dec 28 '16 at 14:47





Please edit your post to include your (suitably redacted) wp-config.php

– muru
Dec 28 '16 at 14:47













The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

– muru
Dec 28 '16 at 15:35





The screenshot explains it better - your iptables rules only allow outgoing traffic for connections initiated from outside. So requests from the server to Wordpress.org would be blocked.

– muru
Dec 28 '16 at 15:35













Ok thanks I would change the rules now and see if it works.

– Raphael Teubner
Dec 28 '16 at 15:37





Ok thanks I would change the rules now and see if it works.

– Raphael Teubner
Dec 28 '16 at 15:37










1 Answer
1






active

oldest

votes


















0














Are your server called wordpress.org ?



According to your config file it's:



server_name 192.168.1.3; #ipaddress;


If you want to use a servername locally, you would have to enter ip-address and name into /etc/hosts, and if it must be accessible externally, you must have a hostname and dns-entry by your ISP. And you must set the appopriate port-forwarding in your router.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f865433%2fhttp-error-curl-error-7-failed-to-connect-to-wordpress-org-port-80%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Are your server called wordpress.org ?



    According to your config file it's:



    server_name 192.168.1.3; #ipaddress;


    If you want to use a servername locally, you would have to enter ip-address and name into /etc/hosts, and if it must be accessible externally, you must have a hostname and dns-entry by your ISP. And you must set the appopriate port-forwarding in your router.






    share|improve this answer




























      0














      Are your server called wordpress.org ?



      According to your config file it's:



      server_name 192.168.1.3; #ipaddress;


      If you want to use a servername locally, you would have to enter ip-address and name into /etc/hosts, and if it must be accessible externally, you must have a hostname and dns-entry by your ISP. And you must set the appopriate port-forwarding in your router.






      share|improve this answer


























        0












        0








        0







        Are your server called wordpress.org ?



        According to your config file it's:



        server_name 192.168.1.3; #ipaddress;


        If you want to use a servername locally, you would have to enter ip-address and name into /etc/hosts, and if it must be accessible externally, you must have a hostname and dns-entry by your ISP. And you must set the appopriate port-forwarding in your router.






        share|improve this answer













        Are your server called wordpress.org ?



        According to your config file it's:



        server_name 192.168.1.3; #ipaddress;


        If you want to use a servername locally, you would have to enter ip-address and name into /etc/hosts, and if it must be accessible externally, you must have a hostname and dns-entry by your ISP. And you must set the appopriate port-forwarding in your router.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 28 '16 at 14:46









        Soren ASoren A

        3,3121924




        3,3121924






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f865433%2fhttp-error-curl-error-7-failed-to-connect-to-wordpress-org-port-80%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Questions related to Moebius Transform of Characteristic Function of the Primes

            List of scandals in India

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?