Error 500 when creating a share using a reserved name

[lacho]

Hi! I created a testing share using a reserved name, I left it running in background but when I restarted the system (I’m using Linux) the name seems to be locked:

zrok2 share public 8080 -n public:<my name>
[ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError "")

I tried deleting the name and creating it again and it didn’t work. I also tried disabling the zrok account and enabling it again using the token, but it didn’t work either. Later, I reserved a new name, but this time I didn’t run the share command in background. I did it from a remote terminal, but when the remote session was closed (unexpectedly, due to a problem on the client computer), I got the same problem, a 500 error when trying to create the share again. I waited some days expecting it to be cleaned, but the error still persists.

Thanks in advance!

[lacho]

I just saw this topic and it is quite similar:

Reserving a service with a specific name returns error 500

Lately I’ve been trying to recreate my service’s reserve because I’ve switched devices, but when I tried to run the command “zrok reserve public 5000 --unique-name onixsb”, it responded with “[ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError)”. I could reserve a different unique name just fine, and I won’t get error 500! It’s just this one that doesn’t want to reserve and throws this error. If that unique name was already taken, then it would’ve…

I tried the solutions mentioned there but they didn’t work. The share names I’m using are medquid and medquid2.

@michael.quigley