That’s awesome! We’ll add it to Routstr.com!
There’s some problem while using with Tor browser. Will fix it soon.
That’s awesome! We’ll add it to Routstr.com!
There’s some problem while using with Tor browser. Will fix it soon.
Thank you! I believe I have everything setup correctly although I know the project is advancing to ppq with cashu soon. The documentation is not very straightforward. I have used grok4 for the past week trying to get this configured correctly. The service appears to be up and running on a hidden tor service.
I set an .env file, a models file and a simple config.json file and ran the docker build. Grabbed my onion url endpoint and posted it to nostr for y'all to see.
I am not able to load the localhost admin page but can load the localhost and the localhost/docs page. I cannot load the onion url or the onion/admin url in a tor browser.
I sent out a curl -X post to my onion url with a cashu token as auth and it paid out the token, sent the request but didn't get an answer back besides "redirecting"
I successfully announced my service to the nostr relays I believe and set my mint and lightning address.
Sounds like a just a tor fix on your end. Anything else should I be looking at as a proxy provider?
Nice !!
One think to make sure ur server can be reached, try to collect ur models.
a GET request to this endpoint '/v1/models'
I saw you had been added to routstr. Nice!
Can you help with a little more specific information as to what you mean? Still figuring this out.
Sure, I mean to make sure ur server is reachable u could do this simple test
curl -X GET https://embeekttrsdquyyicngh5i6xc6xkqymm6cihgzngtbxpoevd6ut5pead.onion/v1/models
That should return the list of all models in ur models.json file
u could also get the the server logs. First navigate to the folderwhere ur docker compose file is located and run the followingcommand
$ docker compose logs
Thanks, doesn't seem to work. Perhaps this is related to using a Tor hidden service url and the above mentioned issue with tor browser. Will keep plugging away and perhaps expose a different provider not over tor in the meantime.
docker compose logs show 100% boot strapped and no errors...besides just a lot of binance api price errors. the docker compose ps shows the routstr proxy and the routstr proxy tor both up for 21 hours.