[系统自带的文件管理器进入appdata目录无限等待]

我也是遇到这个问题，我不仅仅是这么目录，其他的目录用自带的文件管理器进去都这个样子

[500 Internal Server Error]

On 2022/8/16 at AM4点30分, ZION said:

我不确定为什么这很难找到或回答，但这里是如何在不重新启动机器的情况下更正错误。

在控制台中，使用 Root 帐户登录到终端。登录后键入以下命令：

/etc/rc.d/rc.php-fpm 重启

完毕。您现在可以通过 WebUI 重新登录。

其他有用的 Unraid 命令可以在这里找到：

https://selfhosters.net/commands/

 

On 2022/8/16 at AM4点30分, ZION said:

我不确定为什么这很难找到或回答，但这里是如何在不重新启动机器的情况下更正错误。

在控制台中，使用 Root 帐户登录到终端。登录后键入以下命令：

/etc/rc.d/rc.php-fpm 重启

完毕。您现在可以通过 WebUI 重新登录。

其他有用的 Unraid 命令可以在这里找到：

https://selfhosters.net/commands/

Thanks, this method works for me

[[Support] Nginx Proxy Manager (NPM) Official]

On 9/14/2021 at 12:45 AM, mgutt said:

That happens, because NPM talks to an online API to get the recent list of this IP addresses. As you can see here, it tries to access three different URLs:

https://github.com/jc21/nginx-proxy-manager/blob/b39a59ce72eb032d5b725dce90dd6f3cf08b7d29/backend/internal/ip_ranges.js

 

And this is done every 6 hours, so it will happen again even if you don't restart the container😒

 

Maybe you should try to open all three URLs through your PC and solve the captcha (if it hopefully will be shown) to "unlock" your public ip address for accessing them:

https://ip-ranges.amazonaws.com/ip-ranges.json
https://www.cloudflare.com/ips-v4
https://www.cloudflare.com/ips-v6

 

Or try to lock the file with the following command:

su
chattr +i /etc/nginx/conf.d/include/ip_ranges.conf

 

A file with the "i" flag can't be modified or deleted.

 

Optional: If you need to make it editable again:

chattr -i /etc/nginx/conf.d/include/ip_ranges.conf

 

 

I also encountered this problem, when I run this command it prompts me

【/tmp # chattr -h
sh: chattr: not found
/tmp # su
/tmp # whoami
root
/tmp # chattr +i /etc/nginx/conf.d/include/ip_ranges.conf
ash: chattr: not found
/tmp # 】

[[Support] Djoss - Nginx Proxy Manager]

On 12/13/2021 at 8:41 PM, mattie112 said:

Open console

 

Then do:

 

And check if anything is "corrupted" in that file. The first number is the line number (your error lists 300 so look around that).

 

You can also delete and reinstall the container if you have only a single site you can easily reconfigure.

Thank you very much, I think I found the problem. The data in line 300 seems to be incorrect. Should I delete the content below line 300?

On the left is docker logs, and on the right is the content of "cat -n /etc/nginx/conf.d/include/ip_ranges.conf".

 

 

I entered docker, deleted the content after 300 lines, nginx worked normally, but whenever I restart nginx, the content of this configuration file will be updated again, and then the above error appears, I think this should be abnormal. I don't know if I should report this problem, it seems that only I encountered it, or I need to write a script to modify the configuration file whenever nginx starts.

[[Support] Djoss - Nginx Proxy Manager]

18 hours ago, alexleohy said:

我最近在用。第一次下载后可以打开管理界面，但是重启后就会出现问题。之后就无法打开管理界面了。请救救我谢谢

 

18 hours ago, mattie112 said:

您可以尝试为该容器打开一个 shell，然后检查该文件以查看有什么问题。

 

您是否创建了任何自定义配置？或者也许是 IP 地址的白名单？可能是打字错误什么的。

I don’t have this file in my configuration. This is the first time I use it. After I added the certificate, it couldn’t be used. The error I saw from the background

[[Support] Djoss - Nginx Proxy Manager]

I am using it recently. After the first download, the management interface can be opened, but after restarting, there will be problems. After that, the management interface cannot be opened. Please save me thanks