CrewLink-server icon indicating copy to clipboard operation
CrewLink-server copied to clipboard

Custom Voiceserver crashing v1.2.0

Open AzraAnimating opened this issue 3 years ago • 5 comments

When a Voiceserver that isn't the default (crewl.ink) is selected Crewlink Crashes and the Window just turns grey.

I have checked my Server files, they're all up to date.

AzraAnimating avatar Dec 29 '20 15:12 AzraAnimating

I have had this problem with the default server for CrewLink so I believe it may be a bug

olijeffers0n avatar Dec 29 '20 16:12 olijeffers0n

if the voice server is crashing and you're using heroku look at the logs when you start the app (If the issue shows something about the ADDRESS ENV variable there's a fix)

If your issue is the env variable you can go to your heroku settings, show environment variables

add ADDRESS to the key and your url to the pair, that should fix the server issues (If your error is that)

Otherwise, checking the heroku logs and showing us what they say would probably help

jlvivero avatar Dec 29 '20 18:12 jlvivero

if the voice server is crashing and you're using heroku look at the logs when you start the app (If the issue shows something about the ADDRESS ENV variable there's a fix)

If your issue is the env variable you can go to your heroku settings, show environment variables

add ADDRESS to the key and your url to the pair, that should fix the server issues (If your error is that)

Otherwise, checking the heroku logs and showing us what they say would probably help

It seems to me they were saying the client was crashing. I got this issue as well when my server was outdated, but it stopped greyscreening when the server updated. Unfortunately I ran into other issues from there.

henry232323 avatar Dec 30 '20 03:12 henry232323

oh that makes sense, since it was on the server repo, I thought it was talking about the issue I also had with the Address ENV when setting up the server on heroku.

Editing -> my answer would be the workaround for #127 instead

jlvivero avatar Dec 30 '20 06:12 jlvivero

add ADDRESS to the key and your url to the pair, that should fix the server issues (If your error is that)

Can confirm this worked for me. Thanks!

pokropski avatar Dec 30 '20 09:12 pokropski