Hi，
Yep I think the header is the cause too. I modify the configuration but it
still gets 403 error,
which I consider that the header may not be transferred to the backends.
But if I set it to level 4 rather than level 7, nginx works well.
Mark Kirkwood 于2020年9月3日周四 下午12:53写道：
> I think you
I think you might need to set some headers. Here is what we use
(connecting to Swift, but should be generally applicable). We are
running nginx and swift (swift proxy server) on the same host. but again
maybe some useful ideas for you to try (below).
Note that we explicitly stop nginx writing
Zhenshi Zhou wrote:
Thanks for the reply. Here is my nginx configuration.
Did I miss something or is there some special option to set?
What's more, our Flink can work well by connecting to the frontend.
Can you see nginx's error log when there is connection error happening
in java client?
Hi Tom
Thanks for the reply. Here is my nginx configuration.
Did I miss something or is there some special option to set?
What's more, our Flink can work well by connecting to the frontend.
[image: image.png]
Tom Black 于2020年9月3日周四 上午8:13写道：
> It seems like your nginx has the wrong
It seems like your nginx has the wrong configuration for reverse proxy
of S3.
Thanks.
Zhenshi Zhou wrote:
this is ES error log：
{
"error": {
"root_cause": [
{
"type": "repository_verification_exception",
"reason": "[test] path is not accessible on master
this is ES error log：
{
"error": {
"root_cause": [
{
"type": "repository_verification_exception",
"reason": "[test] path is not accessible on master node"
}
],
"type": "repository_verification_exception",
"reason": "[test] path is not accessible on
Zhenshi Zhou wrote:
My fellows wanna use ceph rgw to store ES backup and Nexus blobs.
But the services cannot connect to the rgw with s3 protocol when I
provided them with the frontend nginx address(virtual ip). Only when
they use the backend rgw's address(real ip) the ES and Nexus works
well
