简体   繁体   English

在 Synology nginx 反向代理后面不允许 Zammad 社区零星错误 405

[英]Zammad Community sporadic Error 405 Not Allowed behind Synology nginx Reverse Proxy

This morning I get sometimes irregularly the 405 Not Allowed error message on my Zammad Community App !今天早上我有时会在我的 Zammad 社区应用程序上不定期地收到405 Not Allowed错误消息!

== Info ==信息

  • Ubuntu 20.04LTS Ubuntu 20.04LTS
  • Apache/2.4.41阿帕奇/2.4.41
  • Zammad Community 3.4.x Zammad 社区 3.4.x
  • ElasticSearch 7.8.1 Deb ElasticSearch 7.8.1 Deb
  • Synology DSM 6.2.3.25426 Synology DSM 6.2.3.25426

== Error details ==错误详情

Error 405 on modal with the tag <center>nginx</center> in response.带有标签<center>nginx</center>的模态错误 405 作为响应。

错误 405 不允许 Zammad 社区

It is, weird because I am using Apache and not nginx.这很奇怪,因为我使用的是 Apache 而不是 nginx。

== Apache conf == Apache 配置

Listen 4000

<VirtualHost *:4000>

    ServerName        int-srv-1

    HostnameLookups   Off
    UseCanonicalName  Off
    ServerSignature   Off

    ProxyRequests     Off
    ProxyPreserveHost On

    <Proxy int-srv-1:3000>
        Require local
    </Proxy>
    
    ProxyPass /assets !
    ProxyPass /favicon.ico !
    ProxyPass /robots.txt !
    ProxyPass /ws ws://127.0.0.1:6042/
    ProxyPass / http://127.0.0.1:3000/

    DocumentRoot "/opt/zammad/public"

    <Directory "/">
        Options FollowSymLinks
        AllowOverride None
    </Directory>

    <Directory "/opt/zammad/public">
        Options FollowSymLinks
    Require all granted
    </Directory>

</VirtualHost>

But we use a "built-in" Reverse Proxy running our Synology NAS called "App Portal" to access this awesome helpdesk from outside the network (with fixed IP) available at https://hello.ourdomain.ext as the following:但是我们使用“内置”反向代理运行我们的 Synology NAS,称为“App Portal”,从https://hello.ourdomain.ext提供的网络外部(具有固定 IP)访问这个很棒的帮助台,如下所示:

== Synology NAS conf == Synology NAS 配置

用于 Zammad 社区的 Synology NAS 反向代理配置

用于 Zammad 社区的 Synology NAS 反向代理配置 - 常规

用于 Zammad 社区的 Synology NAS 反向代理配置 - 高级设置

So, I think Synology is answering this Error message because it uses nginx (I believe).所以,我认为Synology 正在回答此错误消息,因为它使用 nginx(我相信)。

But Why?但为什么?

Does HSTS or HTTP/2 could help? HSTS 或 HTTP/2 有帮助吗?

For the moment, a workaround seems to work.目前,一种解决方法似乎有效。

The increase of timeout from 60 to 120sec on the advanced proxy options (Reverse Proxy Rules > Advanced Settings) seems to be paying off.高级代理选项(反向代理规则 > 高级设置)的超时时间从 60 秒增加到 120 秒似乎得到了回报。

反向代理规则高级设置超时增加

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM