Open mja87 opened 4 years ago
Hmmm, I think the healthcheck might be broken because this issue of the container appearing unhealthy has been raised before... We might have to try a different healthcheck...
However this error is actually NOT an issue, it's a red herring... just something Java complains about Spring. It's relatively harmless (for now)
WARNING: An illegal reflective access operation has occurred,
WARNING: Illegal reflective access by org.springframework.boot.loader.jar.Handler (file:/var/airsonic.war) to constructor sun.net.www.protocol.jar.Handler(),
WARNING: Please consider reporting this to the maintainers of org.springframework.boot.loader.jar.Handler,
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations,
WARNING: All illegal access operations will be denied in a future release,
In short, I think the container is fine, even if it appears unhealthy
You're absolutely right, I can connect to -my nas IP-:4040 and it comes right up. I guess I saw the error in the logs and got a 404 when trying to go to music.-mydomain-.com and erroneously connected the two, sorry about that.
It looks like it must be yet another problem with my reverse proxy set up. I guess I get to spend more hours banging my head against the Traefik wall. It doesn't even feel worth it any more!
Thanks for your help.
Having the same warning in my Log. I installed this image on docker Synology.
2020-05-05 11:46:31.462 INFO --- org.airsonic.player.Application : Detected Tomcat web server stdout 09:46:39 WARNING: An illegal reflective access operation has occurred stdout 09:46:39 WARNING: Illegal reflective access by org.springframework.boot.loader.jar.Handler (file:/var/airsonic.war) to constructor sun.net.www.protocol.jar.Handler() stdout 09:46:39 WARNING: Please consider reporting this to the maintainers of org.springframework.boot.loader.jar.Handler stdout 09:46:39 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations stdout 09:46:39 WARNING: All illegal access operations will be denied in a future release stdout 09:46:45 2020-05-05 11:46:45.167 WARN --- o.a.p.s.GlobalSecurityConfig : Generating new encryption key password stdout 09:46:45
Reverse proxy works fine for me!
You're absolutely right, I can connect to :4040 and it comes right up. I guess I saw the error in the logs and got a 404 when trying to go to music..com and erroneously connected the two, sorry about that.
It looks like it must be yet another problem with my reverse proxy set up. I guess I get to spend more hours banging my head against the Traefik wall. It doesn't even feel worth it any more!
Thanks for your help.
Have you tried to add this to your airsonic.properties file?
server.use-forward-headers=true
That did the trick for me to get reverse proxy working.
This is a good point, perhaps it should be incorporated out of the box.
Note that the property is deprecated:
server.use-forward-headers=true
and is replaced by:
server.forward-headers-strategy=framework
or server.forward-headers-strategy=native
Please do make that out of the box. I just spent three hours to finally stumble upon this right before giving up on Airsonic Advanced entirely
Problem description
I'm a noob running Airsonic-Advanced through an OpenMediaVault docker, then through a Traefik 2 reverse proxy. 10.6 was working fine but something seems to have broken recently. The logs I see are below (first post on github, apologies if I screw something up):
Steps to reproduce
System information
Additional notes
I'm a gigantic noob to all of this, but I've really enjoyed your project and appreciate any help.