-
I'm using Vercel for my main website, and I decided to use a detached docker container running on a DigitalOcean droplet to try and get quirrel working. I got it working in localhost no problem, by using When I'm going to the Quirrel UI, for some reason I can never connect to the external host. Sending off an
This is my
I have all of my
I've tried tons of variations of different things at this point, so not really sure what I'm doing wrong. My guess is that something is going wrong with the secure message transfer. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
That was my first idea, as well. Quirrel's 9181 listens via HTTP. Since you specified The hacky solution is to specify the protocol ( |
Beta Was this translation helpful? Give feedback.
-
Tried the Found another solution that lets me relay requests with just an HTTP call in 5mins, went with that instead. Thanks for the help, wish I didn't just barely miss the hosted solution for Quirrel :( |
Beta Was this translation helpful? Give feedback.
That was my first idea, as well. Quirrel's 9181 listens via HTTP. Since you specified
QUIRREL_API_URL
without a protocol, it will default tohttps
.The hacky solution is to specify the protocol (
http://(my-ip):9181
). The right solution is to add a HTTPS-Proxy in front of Quirrel (super easy to do using something like Caddy).