if I work with the old node (Amazon s3 connection (legacy) ), it works and I can also select directories.
If i use the two new connection nodes, the authentication part works, while the connection part doesn’t (it seems that the connection part doesn’t use the manual proxy setting, and I don’t know how to setting this, I can’t find settings in advanced).
thanks for running tests with multiple setups. It is indeed very interesting that the legacy connection works. To be sure that this is indeed a proxy issue, is there a way for you to test the connection without a proxy?
I was not able to find any issues with the S3 Connector in combination with proxies. Still, could you confirm which version of KNIME you’re using? Should you be on an older version, could you test with a current version found here?
Another thing to try is to set up the proxy in Windows instead of KNIME and set the proxy configuration to “Native”.
If Marvin’s solution above doesn’t get you there, it might be necessary to involve our enterprise support and/or partners. If you need help identifying a partner, let us know and someone can reach out to you for further assistance.
thanks for following up and running further tests.
I’m afraid this looks to be a niche issue on a network level. It isn’t obvious to me why this would only impact the newer nodes, but this would require a more detailed investigation. Again, we are happy to put you in contact with partners of ours should you want further assistance debugging.
