Using a S3Connector on our FME2019 desktop using an authenticated S3 connection I get the following message.
I have Cloudberry connected to the S3 bucket on this same machine and it works using the same authentication details.
Could it be our authenticated firewall proxy? Or is it something else?
Hi @peterkt,
Can share which proxy settings you are using? Currently, only Basic Authentication and No Authentication proxies are supported for the S3Connector.
If you configured a system proxy on your machine you will need to configure FME Desktop to use the proxy as well. Please follow these steps in our documentation to do so:
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_IntegrationConsole/Workbench/options-network-proxy.htm
Hi @peterkt,
Can share which proxy settings you are using? Currently, only Basic Authentication and No Authentication proxies are supported for the S3Connector.
If you configured a system proxy on your machine you will need to configure FME Desktop to use the proxy as well. Please follow these steps in our documentation to do so:
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_IntegrationConsole/Workbench/options-network-proxy.htm
We are using basic authentication (see below)
I no doubt I have regular trouble with our firewall proxy. Most traffic eventually gets through and FME2019 appears to be more compatible than 2016.
I also have a lot of workbenches that are successfully connecting to external web services on this machine.
I just want to point the finger at the proxy so want to rule out other possibilities. I have two other S3 methods on the machine that work - cloudberry and a codeplex standalone s3 app.
That error message didn't obviously point at the proxy. Or is that message just saying it can't obtain the SSL connection because it can't get through the proxy?
We are using basic authentication (see below)
I no doubt I have regular trouble with our firewall proxy. Most traffic eventually gets through and FME2019 appears to be more compatible than 2016.
I also have a lot of workbenches that are successfully connecting to external web services on this machine.
I just want to point the finger at the proxy so want to rule out other possibilities. I have two other S3 methods on the machine that work - cloudberry and a codeplex standalone s3 app.
That error message didn't obviously point at the proxy. Or is that message just saying it can't obtain the SSL connection because it can't get through the proxy?
Did you use our old S3 transformers in FME 2016 with the same proxy and did this work as expected?
I haven't seen this specific error before and our QA department tested the S3Conenctor with Basic & NoAuth proxies in house, but if you can confirm that this was working before, we could start to look at differences in the proxy handling to get to the bottom of this.