v5.0.0 on Docker: hostname without protocol in resources

[ghost]

Please confirm you have done the following before posting your bug report:

• I have enabled debug mode
• I have read checked the Common Issues page

Describe the bug
In v5.0.0 Docker image in a Rancher2 envirnment with tls-terminating nginx ingress some resources like js and css have the hostname without https://, so they won't load.

APP_URL and TRESTED_PROXIES variable are correctly set, v 4.9.x was working right before the upgrade

Screenshots
If applicable, add screenshots to help explain your problem.

Server (please complete the following information):

• Snipe-IT Version: v5.0.0
• ENV: Official Docker COntainer

[ghost]

Update: the problem semmes to be that APP_TRUSTED_PROXIES is ignored, because editing config/trustedproxy.php by hand correct the problem.

Anyway in a docker environment this is not the right solution.

[mahdi]

Yes, editing /var/www/html/config/trustedproxy.php and uncommenting 'proxies' => '*', will temporarily fix the issue but as @cobra1978 said this issue should be generally fixed.

[fashberg]

Hey!
Same for me.

copying APP_TRUSTED_PROXIES from ENV to settings has been removed at commit 533649f

Diff:
533649f#diff-65b9650370ce063c0ae4c2d172d40fb6aafd2d2e8fe478dae7da21732d4d36dd

removed code:

    'proxies' => env('APP_TRUSTED_PROXIES') !== null ?
        explode(',', env('APP_TRUSTED_PROXIES')) : '*',

Especially for Docker environments we need this ENV settingg

Kind Regards
Folke

[mschmidt291]

Yes, can also confirm. Running Snipe-IT through our Snipe-IT Helm Chart behind the nginx ingress controller results in css and js loading issues. Uncommenting the line in trustedproxy.php stated above, works fine.

[Sylencer91]

This doesn't help me. Editing /var/www/html/config/trustedproxy.php and uncommenting 'proxies' => '*', doesn't fix my problem. It is still here. Any Idea?