Bitnami 웹서버 세팅 설정문제 문의

Based on the information provided, it appears you're experiencing an issue where your WordPress REST API endpoint is returning an empty payload when receiving POST requests from Make.com, despite working correctly when accessed through a browser.

This type of issue could be related to several factors:

1. Security Group or Network Configuration: While you mentioned port 443 is open, there might be specific security rules or network configurations blocking or dropping connections from Make.com's IP addresses.

2. Application Load Balancer Configuration: If you're using a private ALB (Application Load Balancer), it might not be properly configured to handle external POST requests from third-party services like Make.com.

3. WordPress Configuration: Your WordPress installation might have security plugins or settings that are filtering or blocking API requests from external services.

4. Server Resource Limitations: The server might be experiencing connection limits, causing it to drop connections when there are too many simultaneous requests.

Possible solutions to try:

1. Check your server logs for any specific errors related to these connections.

2. If using an ALB, consider configuring it to properly forward traffic from Make.com to your WordPress instance.

3. Temporarily disable any WordPress security plugins to see if they're causing the issue.

4. Implement proper retry logic in your Make.com scenario to handle potential temporary connection issues.

5. Consider using API Gateway as an intermediary between Make.com and your private application if you need to maintain your current architecture.

If the issue persists, you might need to examine your server's connection handling configuration to ensure it's not prematurely closing connections from external services.
Sources
Allow public IPs to reach an internal app that is behind a private ALB | AWS re:Post
Bedrock eu-north-1 stockholm down with http 503, AWS health green | AWS re:Post