Nice !!

One think to make sure ur server can be reached, try to collect ur models.

a GET request to this endpoint '/v1/models'

Reply to this note

Please Login to reply.

Discussion

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.