@i207M commented on GitHub:
Thanks for your help.
After some digging, the underlying issue is, user --https--> nginx --http--> transfer.sh, so the backend receives request in http protocol.…
@Skillkiller commented on GitHub:
I have no problem reaching the website from Germany @AwesomeKalin
@AwesomeKalin commented on GitHub:
It's happening again, although this time it's my fault for uploading lots of small files
@stefanbenten commented on GitHub:
It's happening again, although this time it's my fault for uploading lots of small files
The server does not have any issues based on monitoring or logs. I…
@cayenne17 commented on GitHub:
Did it crash again? @stefanbenten
It works for me.
You have to put HTTPS and not just HTTP. I see that it doesn't respond in HTTP port 80.
I don't know…
@aidanlok commented on GitHub:
Can confirm, does not work from USA either, using HTTP or HTTPS.
@itseyup commented on GitHub:
Did it crash again? @stefanbenten
It works for me.
You have to put HTTPS and not just HTTP. I see that it doesn't respond in HTTP port 80.
I…
@Skillkiller commented on GitHub:
The website is also not accessible from Germany. At 3 p.m. the site was still reachable.
@cayenne17 commented on GitHub:
it doesn't work for me either. it can't resolve the transfer.sh domain name.
it seems to be a problem with the NIC of the .sh zone
dig @1.1.1.1 …
@dillfrescott commented on GitHub:
Stumbled upon https://transfersh.com/. Is this official?
@paolafrancesca commented on GitHub:
but created link is returned without newline, so it is not easy to copy.
indeed it's easy with
curl -T </path/to/file> <transfer_sh_endpoint>