Black listed by heroku
10maurycy10 opened this issue · comments
If you try to upload this app heroku complains about the AUP.
Changing the names and the url in Dockerfile should resolve this.
See my fork https://github.com/10maurycy10/chisel-heroku
I have the same; however, changing names etc in the Dockerfile still prevents chisel from starting. From the logs:
heroku[web.1]: Starting process with command `/bin/sh -c /bin/sheep\ server\ --auth\ \user:pass\ --socks5\ --reverse`
app[web.1]: 2022/04/25 12:10:37 server: Reverse tunnelling enabled
app[web.1]: 2022/04/25 12:10:37 server: Fingerprint <REDACTED>
app[web.1]: 2022/04/25 12:10:37 server: User authenication enabled
app[web.1]: 2022/04/25 12:10:37 server: Listening on http://0.0.0.0:30289
app[web.1]: Killed
heroku[web.1]: Process exited with status 137
heroku[web.1]: State changed from starting to crashed
seems like a new black list attempt.
I have bypassed it by replacing all instances of chserver, chshared and chclient with hhserver, hhshared and hhclient. Then running docker build . -t horse -f ./Dockerfiile and extracting the build file from docker.
Dear Maurycy, thanks for the tips! it worked perfectly. Greetings!
Hey!
Would using your repo work or should I fork it and modify it?
Thank you :)
With this workaround you should be able to set up the instance. But you still need to use the http proxy instead of socks proxy, because Heroku now disallows the socks5 proxy from ssh. (stream error ssh rejected administratively prohibited (socks5 is not enabled))
ooh well it won't work for my use then :/