Reactjs Nginx服务器在我的React路由器应用程序中返回404
好的，我已经在Digital Ocean安装了一台nginx服务器。我在机器中使用了React路由器的React应用程序 问题是除了Reactjs Nginx服务器在我的React路由器应用程序中返回404,reactjs,nginx,react-router,Reactjs,Nginx,React Router,好的，我已经在Digital Ocean安装了一台nginx服务器。我在机器中使用了React路由器的React应用程序 问题是除了'/'之外的任何url都返回404错误 我知道有数百万条类似的线索，但在网上找到的答案都不能解决我的问题。您会注意到，在我的代码中有一些关于这些解决方案的注释 您可以在下面找到我的nginx文件（请注意，我有3个子域）： /etc/nginx/sites available/madscale.gr server { root /var/www/ma
'/'404错误
我知道有数百万条类似的线索，但在网上找到的答案都不能解决我的问题。您会注意到，在我的代码中有一些关于这些解决方案的注释
您可以在下面找到我的nginx文件（请注意，我有3个子域）：
/etc/nginx/sites available/madscale.gr
server {
root /var/www/madscale.gr/madbuild/build;
index index.html index.htm index.nginx-debian.html;
server_name madscale.gr www.madscale.gr;
location /app1 {
try_files $uri $uri/ /index.html;
proxy_pass http://localhost:8086;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/madscale.gr/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/madscale.gr/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 {
root /mad_admin/build;
index index.html index.html index.nginx-debian.html;
server_name admin.madscale.gr;
location /app2 {
proxy_intercept_errors on;
error_page 404 = /index.html;
#root /mad_admin/build;
# try_files $uri index.html;;
try_files $uri #uri/ index.html;
# try_files $uri $uri/ /index.html$is_args$args;
proxy_pass http://localhost:8083;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
# listen [::]:80 ; # managed by Certbot
# listen 80 ; # managed by Certbot
# ssl_certificate /etc/letsencrypt/live/admin.madscale.gr/fullchain.pem; # managed by Certbot
# ssl_certificate_key /etc/letsencrypt/live/admin.madscale.gr/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
listen [::]:443 ssl; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/madscale.gr/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/madscale.gr/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 {
root /testmad_web/build;
index index.html index.htm index.nginx-debian.html;
server_name test.madscale.gr;
location /app3 {
try_files $uri $uri/ /index.html;
# try_files $uri /index.html;
proxy_pass http://localhost:8087;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
listen 80; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/madscale.gr/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/madscale.gr/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.madscale.gr) {
return 301 https://$host$request_uri;
} # managed by Certbot
if ($host = madscale.gr) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
listen [::]:80;
server_name madscale.gr www.madscale.gr;
return 404; # managed by Certbot
}
#server {
# if ($host = admin.madscale.gr) {
# return 301 https://$host$request_uri;
# } # managed by Certbot
# listen 80;
# listen [::]:80;
# server_name admin.madscale.gr;
# return 404; # managed by Certbot
#}
/etc/nginx/可用站点/默认
# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
root /var/www/html;
#root /mad_admin/build;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# root /usr/share/nginx/html;
#index index.html index.htm;
try_files $uri /index.html;
# try_files $uri $uri/ /index.html;
# try_files $uri index.html;
# try_files $uri $uri/ /index.html;
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
##try_files $uri $uri/ =404;
}
location ^~ /app2 {
root /mad_admin/build;
try_files $uri $uri/ index.html;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.0-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 admin.madscale.gr;
# root /mad_admin/build;
# index index.html;
# location / {
# try_files $uri $uri/ /index.html;
# try_files $uri $uri/ =404;
# }
#}
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}
您必须使用hashRouter
或在服务器端将所有404重定向到index.html
并在客户端处理该问题，那么您关心的是哪个域？try\u文件在某些位置中。因此，所有位置都从您配置的位置开始。如果没有，您应该尝试将try_文件
移动到location/{}
并check@Panther如果我让他们中的一个工作，我会让其他人也：）但我在玩管理员one@Panther你的意思是站点可用/默认文件中的位置/
？不。对于您添加的每个站点location/app1
，每个服务器都应该有location/
，您可以在其中定义try\u文件
，但是如果您的url都以/app1
开头，那么对于特定的域，情况就不同了。HashRouter
不起作用，我（认为）我已经尝试将404
重定向到index.html
，除非我做了什么蠢事。。