-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No link returned from self-hosted server #1
Comments
Hi, are you using any sort of proxy (like nginx) before the request is routed to skicka? |
Yes, I am using caddy to reverse proxy to the listen port. |
Alright, Caddy is most likely buffering the request/response instead of transmitting it "live" to Skicka - I've had similar issues when using Nginx as a reverse proxy. Try setting |
I'm running with the following directive
and various combinations of removing flush/buffers and still no link. For completeness, I'm testing using |
I tried removing the reverse proxy and it works like a charm. So indeed that's the problem |
Yes, I haven’t been able to get Skicka working with Nginx either and finally just left it working on a separate port. I’ll take a look later, considering Caddy also has issues with forwarding the requests, maybe it’s something in Skicka that triggers this behavior in proxies. |
Alright, I've done some magic refactoring and managed to get Caddy's Please check out and let me know back! |
Still not working for me :(. I pulled and rebuilt and tried with both
and
in both cases the link is still not displayed, but if I change to myserver.com:[port] it does work (so it's still related to the reverse proxy probably). My current directive is just Are you running exposing it on port 80 specifically? Because I'm exposing it under a subdomain, not sure if that matters? |
Ouch 😢 I've been testing it locally under port 80, yeah - I'll try with subdomain as well and we'll see. |
Alright, I've tested it on an actual server using Caddy and it seems to be working correctly, i.e. I've got:
... with Skicka running at
... which immediately shows me a working link; I'm testing it on Caddy 2.8.4. |
Sorry, I just saw your comment. What I'm trying to do is actually not expose the port (
using
This still does not work. It's not a big deal obviously, and thanks again for all the time you're spending on this, but I really don't understand what the problem could be. Sticking the port in front of it in the Caddy directive makes it work (like in your example). |
My example uses What's your version of Caddy? I'm testing on 2.8.4. |
I'm also on 2.8.4. I'm over https, that's the only difference I can see tbh |
Hi, I'm trying to self-host skicka but I cannot get it to work. When I run the example
cat [my-file] | curl --data-binary @- [my-server]
I do not get any link returned. Running the same example against you hosted service does return the link.I tried to visit my server with a get request and it works. Any idea what could be wrong? Maybe some setting on my server machine?
The text was updated successfully, but these errors were encountered: