We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
WHCMS and VESTACP INTEGRATION PROBLEM
-
- Posts: 33
- Joined: Sun Oct 05, 2014 7:53 am
WHCMS and VESTACP INTEGRATION PROBLEM
I have triend to intergrate vetsacp and whmcs.. each time i accept order and run "" then error comes says " 500 internal server error , Sorry, something went wrong :("
this is error log
this is my nginx config i modified a lil bit but still it's not fixed
. anyone knows this fix then please let me know.. thanks
this is error log
Code: Select all
2015/04/22 12:01:37 [error] 5488#0: *13 upstream prematurely closed connection while reading response header from upstream, client: 39.32.18.104, server: greensgaming.com, request: "POST /manager/admin/orders.php?action=view&id=2&activate=true HTTP/1.1", upstream: "http://185.62.188.57:8080/manager/admin/orders.php?action=view&id=2&activate=true", host: "www.greensgaming.com", referrer: "http://www.greensgaming.com/manager/admin/orders.php?action=view&id=2"
2015/04/22 12:01:38 [error] 5488#0: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 39.32.18.104, server: greensgaming.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://185.62.188.57:8080/favicon.ico", host: "www.greensgaming.com", referrer: "http://www.greensgaming.com/manager/admin/orders.php?action=view&id=2&activate=true"
Code: Select all
# Server globals
user nginx;
worker_processes 2;
error_log /var/log/nginx/error.log;
pid /var/run/nginx.pid;
# Worker config
events {
worker_connections 1024;
use epoll;
}
http {
# Main settings
sendfile on;
tcp_nopush on;
tcp_nodelay on;
client_header_timeout 10m;
client_body_timeout 10m;
client_header_buffer_size 200k;
client_body_buffer_size 1024k;
client_max_body_size 1000m;
large_client_header_buffers 4 8k;
send_timeout 60;
keepalive_timeout 120 120;
reset_timedout_connection on;
server_tokens off;
server_name_in_redirect off;
server_names_hash_max_size 1024;
server_names_hash_bucket_size 1024;
# Log format
log_format main '$remote_addr - $remote_user [$time_local] $request '
'"$status" $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
log_format bytes '$body_bytes_sent';
#access_log /var/log/nginx/access.log main;
access_log off;
# Mime settings
include /etc/nginx/mime.types;
default_type application/octet-stream;
# Compression
gzip on;
gzip_comp_level 9;
gzip_min_length 512;
gzip_buffers 8 64k;
gzip_types text/plain text/css text/javascript
application/x-javascript;
gzip_proxied any;
# Proxy settings
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass_header Set-Cookie;
proxy_connect_timeout 300;
proxy_send_timeout 300;
proxy_read_timeout 300;
proxy_buffers 32 128k;
proxy_busy_buffers_size 128k;
proxy_buffer_size 128k;
# Cloudflare https://www.cloudflare.com/ips
set_real_ip_from 199.27.128.0/21;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 104.16.0.0/12;
set_real_ip_from 2400:cb00::/32;
set_real_ip_from 2606:4700::/32;
set_real_ip_from 2803:f800::/32;
set_real_ip_from 2405:b500::/32;
set_real_ip_from 2405:8100::/32;
real_ip_header CF-Connecting-IP;
# SSL PCI Compliance
ssl_session_cache shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";
# Error pages
error_page 403 /error/403.html;
error_page 404 /error/404.html;
error_page 502 503 504 /error/50x.html;
# Cache
proxy_cache_path /var/cache/nginx levels=2 keys_zone=cache:10m inactive=60m max_size=512m;
proxy_cache_key "$host$request_uri $cookie_user";
proxy_temp_path /var/cache/nginx/temp;
proxy_ignore_headers Expires Cache-Control;
proxy_cache_use_stale error timeout invalid_header http_502;
proxy_cache_valid any 3d;
map $http_cookie $no_cache {
default 0;
~SESS 1;
~wordpress_logged_in 1;
}
# Wildcard include
include /etc/nginx/conf.d/*.conf;
}
Re: WHCMS and VESTACP INTEGRATION PROBLEM
Check your firewall first, try to stop and make tests.
I see on this forum people solved prob like this via correct settings (some errors in WHCMS configs).
I see on this forum people solved prob like this via correct settings (some errors in WHCMS configs).