Unable to Connect Using AMP #697
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#697
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
This is not necessarily an issue with Garage, but I am having issue connecting to it using my AMP server. I tried reaching out to CodeCubers for support, but they seem to believe it is an issue on Garage's end and were not very helpful. I would appreciate any insight anyone may have. I can access my S3 fine using any other means, it is only AMP that has an issue. Here is the error received through the AMP console when trying to upload to the S3:
Using an HTTP connection
Using an HTTPS connection:
Thank you!
Hello @bovive, thanks for filing an issue with us, can you be more specific on what your setup looks like? From my quick reading it seems that you are trying to use garage to host AMP backups. Was garage provided as part of AMP or did you set it up yourself? In the later case, would you explain how your did it?
PS: I allowed myself to slightly edit your issue to make it more readable
makes me thing the HTTP test doesn't work because it's sending HTTP redirects, probably to force HTTPS requests
sounds like a TLS error, maybe the reverse proxy sent the wrong certificate/a self signed certificate/not a full chain going to a root CA.
Closed for inactivity, please reopened if you still have the issue.