• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Plesk starts dropping http connections after a certain amount of requests

M

Marchiuz

New Pleskian
Server operating system version
AlmaLinux 8.4 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.41.1
I have two domains setup on plesk - let's say usersite.com and api.usersite.com. usersite.com is powered by nuxt.js - a front-end framework which runs on node.js. It makes API calls to api.usersite.com, which is a Laravel application powered by Octane (so it uses swoole instead of php-fpm). Both of these projects are running inside docker containers.
Now to the problem - when there is slightly higher traffic to usersite (200 users per minute) API site starts to drop connections, immediately resulting in 504. Perhaps someone could guide me in the right direction of why this might be happening? First I thought it was an issue of php-fpm that's why I've reworked my project and dockerized it to be served by Octane server instead of php-fpm. That doesn't seem to have helped, however. Worth mentioning that nginx is used as reverse proxy. So perhaps it's something to do with nginx limiting request count?
 
Update:
I think it's nginx fault. Since API requests are proxied, they all came from the same ip - server's ip. Once it starts refusing connections, I noticed that I am still able to fire requests and receive proper responses using postman.
 
Marchiuz said:
Update:
I think it's nginx fault. Since API requests are proxied, they all came from the same ip - server's ip. Once it starts refusing connections, I noticed that I am still able to fire requests and receive proper responses using postman.
Click to expand...
I dont thinks so... Nginx out of the box is able to serve hundreds ( or maybe thousands ) of simultaneous requests, you bottleneck must be some place else... What are the nginx logs says? ( proxy_access_ssl , proxy_access_log and proxy and proxy_error_log )
 
Cike76 said:
I dont thinks so... Nginx out of the box is able to serve hundreds ( or maybe thousands ) of simultaneous requests, you bottleneck must be some place else... What are the nginx logs says? ( proxy_access_ssl , proxy_access_log and proxy and proxy_error_log )
Click to expand...
Where may I find these logs?
 
Since the front-end project runs in docker, I can see the logs for it in docker view. Here's an image showing some of the errors.
1664986499236.png

content of proxy_error_log
1665045933017.png

It's weird that latest errors shown in this file are from 09-27 but we're getting the errors every day

@mow My thoughts as well, how could I debug this?
 
Update:
I did fix the "same ip address from proxy" issue, so now proxied requests actually take the ip of the client. But that has not solved my issue :/
 
Marchiuz said:
Update:
I did fix the "same ip address from proxy" issue, so now proxied requests actually take the ip of the client. But that has not solved my issue :/
Click to expand...
That only fixes the logging. The actual connections still come from the proxy.
 
mow said:
That only fixes the logging. The actual connections still come from the proxy.
Click to expand...
Oh, then how may I properly fix it? I assume using nginx as proxy is quite often practice nowadays, how do they deal with such issue?
 
You must log in or register to reply here.
Back
Top