Ошибка 404 не найдена, когда я делаю запрос на публикацию в flask + nginx ⇐ Python

[Anonymous]

Я использую сервер Flask на экземпляре AWS EC2. Экземпляр AWS EC2 означает компьютер на AWS. Я использую эту команду для запуска сервера Gunicorn --bind 0.0.0.0:5000 app:app. Я настроил nginx в качестве обратного прокси-сервера без того же экземпляра EC2. Мой экземпляр EC2 работает под управлением Ubuntu 24.04.3 LTS.
Я получаю ошибку 404 Not Found, когда делаю запрос на публикацию с использованием маршрута https://www.example.com/processing. Я не получаю сообщение 404 Not Found при отправке запроса на https://www.example.com. Я владею доменом www.example.com. что мне делать, чтобы при отправке запроса на публикацию не появлялось сообщение 404 Not Found? Я пробовал много решений из stackoverflow, но ни одно из них не решило мою проблему.
это мой код в app.py
from flask import Flask, request, jsonify
from PIL import Image
import base64
import io

from datetime import timedelta
from flask import make_response, request, current_app, send_file
from functools import update_wrapper

from flask_cors import CORS, cross_origin

app = Flask(__name__)
CORS(app)

@app.route("/")
def hello():
return "Hello, World!"

@app.route('/processing', methods=['POST','OPTIONS'])
@cross_origin()
def process():
print(request.files)
file = request.files['image']

img = Image.open(file.stream)

data = file.stream.read()

data = base64.b64encode(data).decode()
return jsonify({
'msg': 'success',
'size': [img.width, img.height],
'format': img.format,
'img': data
})

Я добавил следующие строки в файл конфигурации nginx
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
proxy_pass http://public-ip-of-ec2-instance:5000/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
try_files $uri $uri/ =404;
}

location /processing {
proxy_pass http://public-ip-of-ec2-instance:5000/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
try_files $uri $uri/ =404;
# OR
# try_files $uri $uri/ @backend;
}

Ниже приведено содержимое файла конфигурации nginx, расположенного в /etc/nginx/sites-available/default .
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/st ... _pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;

# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}

# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/run/php/php7.4-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}

# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}

server {

# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name www.example.com; # managed by Certbot

location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
proxy_pass http://public-ip-of-ec2-instance:5000/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
try_files $uri $uri/ =404;
}

location /processing {
proxy_pass http://public-ip-of-ec2-instance:5000/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
try_files $uri $uri/ =404;
# OR
# try_files $uri $uri/ @backend;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/run/php/php7.4-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}

listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/www.example.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/www.example.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
if ($host = www.example.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80 ;
listen [::]:80 ;
server_name www.example.com;
return 404; # managed by Certbot

}


Подробнее здесь: https://stackoverflow.com/questions/798 ... lask-nginx