So it works ok via iOS using an older TKL version - when behind a reverse proxy!?
Assuming so, could you please confirm which specific TurnKey version? I was going to suggest that it's likely the v17.x release, but the original report was related to v17.x, so probably not? FYI I only need to major version but if you're unsure, you can get it via CLI with:
turnkey-version
It would also be awesome if you could also confirm the software you're using as a reverse proxy and what version that is (e.g. Nginx and the version). The reverse proxy config and setup would also be greatly appreciated.
Regardless, just knowing that it works as expected with a previous version should give me something to work with re this issue - especially if I know which version. I can compare our default config and what has changed between major versions. If nothing there jumps out, I can also look through the changelogs of major software components which may highlight the specific issue? If it seems that it's not specifically related to our config, I can lodge a bug report upstream.
Even if the core issues is outside of what we can do, if we can find a workaround, we can at least document it.
FWIW with this extra info, I suspect that it may be related to some security hardening that we did in v17.x and perhaps v18.x. There is always a risk that tightening the security screws will create issues in some scenarios. And if you are behind a reverse proxy, then our hardening is almost certainly irrelevant as the hardening would best be applied to the outwards facing server - which is obviously outside our control.
Also, if anybody else experiencing this issue could also try an older TurnKey version and confirm that it works as expected with iOS would be awesome.
Ah, so it works ok with iOS on an older TurnKey version!?
So it works ok via iOS using an older TKL version - when behind a reverse proxy!?
Assuming so, could you please confirm which specific TurnKey version? I was going to suggest that it's likely the v17.x release, but the original report was related to v17.x, so probably not? FYI I only need to major version but if you're unsure, you can get it via CLI with:
It would also be awesome if you could also confirm the software you're using as a reverse proxy and what version that is (e.g. Nginx and the version). The reverse proxy config and setup would also be greatly appreciated.
Regardless, just knowing that it works as expected with a previous version should give me something to work with re this issue - especially if I know which version. I can compare our default config and what has changed between major versions. If nothing there jumps out, I can also look through the changelogs of major software components which may highlight the specific issue? If it seems that it's not specifically related to our config, I can lodge a bug report upstream.
Even if the core issues is outside of what we can do, if we can find a workaround, we can at least document it.
FWIW with this extra info, I suspect that it may be related to some security hardening that we did in v17.x and perhaps v18.x. There is always a risk that tightening the security screws will create issues in some scenarios. And if you are behind a reverse proxy, then our hardening is almost certainly irrelevant as the hardening would best be applied to the outwards facing server - which is obviously outside our control.
Also, if anybody else experiencing this issue could also try an older TurnKey version and confirm that it works as expected with iOS would be awesome.