{"action":"created","issue":{"url":"https://api.github.com/repos/restic/restic/issues/393","labels_url":"https://api.github.com/repos/restic/restic/issues/393/labels{/name}","comments_url":"https://api.github.com/repos/restic/restic/issues/393/comments","events_url":"https://api.github.com/repos/restic/restic/issues/393/events","html_url":"https://github.com/restic/restic/issues/393","id":127225530,"number":393,"title":"TLS: Oversized record received","user":{"login":"arvdsn","id":4639602,"avatar_url":"https://avatars.githubusercontent.com/u/4639602?v=3","gravatar_id":"","url":"https://api.github.com/users/arvdsn","html_url":"https://github.com/arvdsn","followers_url":"https://api.github.com/users/arvdsn/followers","following_url":"https://api.github.com/users/arvdsn/following{/other_user}","gists_url":"https://api.github.com/users/arvdsn/gists{/gist_id}","starred_url":"https://api.github.com/users/arvdsn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arvdsn/subscriptions","organizations_url":"https://api.github.com/users/arvdsn/orgs","repos_url":"https://api.github.com/users/arvdsn/repos","events_url":"https://api.github.com/users/arvdsn/events{/privacy}","received_events_url":"https://api.github.com/users/arvdsn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-18T13:21:58Z","updated_at":"2016-01-18T18:41:32Z","closed_at":null,"body":"Hey,\r\n\r\nI've been following the discussions between you an minio and was excited to try it out. Looks like I'm running into a tls issue. \r\n\r\nBackend (minio) is started with `./minio server /mnt/backup/minio/`\r\nFrontend (compiled source) is started with `./restic -r s3://10.0.0.120:9000/mbp13 init`\r\n\r\nResult is: `creating backend at s3://10.0.0.120:9000/mbp13 failed: Put https://10.0.0.120:9000/mbp13?location=: tls: oversized record received with length 20527`\r\n\r\nI also tried to use an existing nginx-proxy routed to /restic/ but then I get this `creating backend at s3://10.0.0.66/restic failed: Put https://10.0.0.66/restic?location=: x509: cannot validate certificate for 10.0.0.66 because it doesn't contain any IP SANs` even with valid self-signed cert.\r\n\r\nI'm probably simply missing something, but I can't figure out what. The bucket is supposed to be created with init, right? "},"comment":{"url":"https://api.github.com/repos/restic/restic/issues/comments/172619639","html_url":"https://github.com/restic/restic/issues/393#issuecomment-172619639","issue_url":"https://api.github.com/repos/restic/restic/issues/393","id":172619639,"user":{"login":"fd0","id":123276,"avatar_url":"https://avatars.githubusercontent.com/u/123276?v=3","gravatar_id":"","url":"https://api.github.com/users/fd0","html_url":"https://github.com/fd0","followers_url":"https://api.github.com/users/fd0/followers","following_url":"https://api.github.com/users/fd0/following{/other_user}","gists_url":"https://api.github.com/users/fd0/gists{/gist_id}","starred_url":"https://api.github.com/users/fd0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fd0/subscriptions","organizations_url":"https://api.github.com/users/fd0/orgs","repos_url":"https://api.github.com/users/fd0/repos","events_url":"https://api.github.com/users/fd0/events{/privacy}","received_events_url":"https://api.github.com/users/fd0/received_events","type":"User","site_admin":false},"created_at":"2016-01-18T18:41:32Z","updated_at":"2016-01-18T18:41:32Z","body":"Hi, thanks for trying the new minio s3 library support!\r\n\r\nThe repository specification (that what you give restic with `-r`) has changed for s3, the old `s3://host/bucket` is still supported, but will try to connect via HTTPS, hence the TLS error.\r\n\r\nPlease try the new (not yet documented *cough*) format like this:\r\n```\r\n$ restic -r s3:http://10.0.0.120:9000/mbp13 init\r\n```"}}