You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to use a non-standard port on my backend, I cannot connect using the pagekite frontend. I get the following error:
>>> Hello! This is pagekite.py v1.5.2.201011. [CTRL+C = Stop]
It looks like your Internet connection might be down! Will retry soon.
- Check whether you can ping pagekite.net or google.com
- Check whether `pagekite.mwt.me` can be looked up in DNS
<< pagekite.py [down] No kites ready to fly. Waiting...
yet, curl pagekite.mwt.me:14678 gives me the "pagekite for pagekite.mwt.me:14678 is unavailable at the moment." page. So I am able to connect to the frontend via the backend. I just can't get pagekite to recognize it. I've tried both with Python 3 and Python 2.
I also have some config files that say the same thing in more lines.
Edit: Running the backend command does not add lines to the frontend log. So, I don't think that a connection is even being attempted. The curl command does add a line to the log.
The text was updated successfully, but these errors were encountered:
mwt
changed the title
Connection fails when backend uses nonstandard port
Connection fails when frontend uses nonstandard port
Nov 11, 2020
When I try to use a non-standard port on my backend, I cannot connect using the pagekite frontend. I get the following error:
yet,
curl pagekite.mwt.me:14678
gives me the "pagekite for pagekite.mwt.me:14678 is unavailable at the moment." page. So I am able to connect to the frontend via the backend. I just can't get pagekite to recognize it. I've tried both with Python 3 and Python 2.Frontend details
Here is my frontend config (~/.pagekite.rc):
and log:
Backend details
I've just been running:
I also have some config files that say the same thing in more lines.
Edit: Running the backend command does not add lines to the frontend log. So, I don't think that a connection is even being attempted. The
curl
command does add a line to the log.The text was updated successfully, but these errors were encountered: