Replying to Avatar utxo the webmaster 🧑‍💻

Can you curl localhost:3334?
Avatar
zach 1y ago

No it returned

curl: (7) Failed to connect to localhost port 3334 after 0 ms: Couldn’t connect to server

Reply to this note

Please Login to reply.

Discussion

Avatar
utxo the webmaster 🧑‍💻 1y ago

something wrong with the service file, run

sudo journalctl -u wot-relay

Should give u good info

Avatar
zach 1y ago

I ran that and it returned:

Then I did: sudo systemctl status wot-relay and it returned the second image:

Avatar
Derek Ross 1y ago

Stop the service and then run the binary manually to see if it starts

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

that confirms that it's not running or was unable to bind to that address/port

try running

sudo systemctl status

it may give you more information, there is also

sudo journalctl -u .service

Avatar
zach 1y ago

Thank you. I tried the systemctl status command and it looks like it’s not running

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

the journalctl command often shows more context and if you read it carefully you may see something, like "permission denied" on reading or writing some file or folder or binding to an address

Avatar
zach 1y ago

I didn’t even know you could open a second terminal and watch everything in real time like that, still very much a noob.

Thank you for your comments!

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i'm a log-watching-addict, i even write my own intensive loggers and stare at them for hours