-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using port other than 80 to host proxy #7
Comments
Heh - That is classic Copy and Paste nonsense. Really should have fixed it. Anyway, it should be possible, but it'll require more than just changing the port. If you know which IP the server is running on you can change the file https://github.com/Podginator/KoboOmnivoreConverter/blob/main/hook/pocket.cc and recompile it, similar to what is said in this file https://github.com/Podginator/KoboOmnivoreConverter/blob/main/hook/README.md then just have 192.168.0.whatever:port and rerun the server on that port number. The original version of this replaced some hardcoded strings in a library, so the port 80 stuff is a remnant of that. |
Ok. I have followed all the steps. Now the server and Kobo seem to see each other, but I still get this error:
Probably a completely different problem now... |
Hi!
Is there any way to not use port 80 for proxy? I'm using my Synology NAS to host the proxy but I already use port 80 on it and I cannot change it.
Is it as easy as just changing this line in
index.js
? Or maybe I need to change the hosts file on my Kobo too?I'm not even going to ask why there are 3 different ports here...
I'm getting this error when running
node ./index.js &
:The text was updated successfully, but these errors were encountered: