[BUG] <title>conf for Seafile Bugs [How to FIXED it]

[PangciPG]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

"The official documentation does not provide a configuration for Seafile. I have researched many related posts and found that everyone is experiencing issues: 400 errors and Bad Request and Contradictory scheme headers errors.

I found a solution. The reason is that Seafile comes with its own Nginx, which includes the same content provided by SWAG:

include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;

This duplication is causing the issue. Simply comment out these two lines and it will resolve the problem. Then, use the simplest default.conf and adjust the $upstream_app and $upstream_port settings, and SWAG will work perfectly. I don't know why, but NPM does not have this problem."

Expected Behavior

"The official documentation does not provide a configuration for Seafile. I have researched many related posts and found that everyone is experiencing issues: 400 errors and Bad Request and Contradictory scheme headers errors.

I found a solution. The reason is that Seafile comes with its own Nginx, which includes the same content provided by SWAG:

include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;

This duplication is causing the issue. Simply comment out these two lines and it will resolve the problem. Then, use the simplest default.conf and adjust the $upstream_app and $upstream_port settings, and SWAG will work perfectly. I don't know why, but NPM does not have this problem."

Steps To Reproduce

The official documentation does not provide a configuration for Seafile. I have researched many related posts and found that almost everyone is experiencing issues: 400 errors or Bad Request and Contradictory scheme headers errors.

I found a solution. The reason is that Seafile comes with its own Nginx, which includes the same content provided by SWAG:

include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;

This duplication is causing the issue. Simply comment out these two lines and it will resolve the problem. Then, use the simplest default.conf and adjust the $upstream_app and $upstream_port settings, and SWAG will work perfectly. I don't know why, but NPM does not have this problem."