I have played around with Pagekite a little. I have an application
running on my localhost which exposes the port 9990 and I want this
port to be available publicly, i.e http://myname.pagekite.me:9990
should be accessible from the 'outside' world. The few attempts I have
made to do that with Pagekite tells me that its probably not allowed
to bind this port.
Is that right? If yes, what's the alternative?
Many thanks!
-Amit
On Sun, Jan 15, 2012 at 8:13 AM, Amit Saha <droi...@gmail.com> wrote:
> Hello all:
>
> I have played around with Pagekite a little. I have an application
> running on my localhost which exposes the port 9990 and I want this
> port to be available publicly, i.e http://myname.pagekite.me:9990
> should be accessible from the 'outside' world. The few attempts I have
> made to do that with Pagekite tells me that its probably not allowed
> to bind this port.
The PageKite service is only listening on some ports, not all (you can
see a list when the program connects to its front-end). You will have
to use one of those. For example, you could connect
http://myname.pagekite.me:8080/ to your localhost:9990 with a
command-line like this:
$ pagekite 9990 http://myname.pagekite.me:8080/
Or to just add that to your default configuration:
$ pagekite --add 9990 http://myname.pagekite.me:8080/
$ pagekite
...
Is the exact number, 9990 important for some reason?
--
Bjarni R. Einarsson
Founder, lead developer of PageKite.
Make localhost servers visible to the world: https://pagekite.net/
On 01/15/2012 11:29 PM, Bjarni R�nar Einarsson wrote:
> Hi Amit!
>
> On Sun, Jan 15, 2012 at 8:13 AM, Amit Saha<droi...@gmail.com> wrote:
>> Hello all:
>>
>> I have played around with Pagekite a little. I have an application
>> running on my localhost which exposes the port 9990 and I want this
>> port to be available publicly, i.e http://myname.pagekite.me:9990
>> should be accessible from the 'outside' world. The few attempts I have
>> made to do that with Pagekite tells me that its probably not allowed
>> to bind this port.
>
> The PageKite service is only listening on some ports, not all (you can
> see a list when the program connects to its front-end). You will have
> to use one of those. For example, you could connect
> http://myname.pagekite.me:8080/ to your localhost:9990 with a
> command-line like this:
>
> $ pagekite 9990 http://myname.pagekite.me:8080/
>
> Or to just add that to your default configuration:
>
> $ pagekite --add 9990 http://myname.pagekite.me:8080/
> $ pagekite
> ...
>
> Is the exact number, 9990 important for some reason?
Many thanks for your reply. Yes, I am trying to host my own App Inventor
service which can only connect to the port:9990 to use as its build
service. So..:)
Well, I think the alternative is to run my own frontend, right? Anything
else?
Thanks again.
-Amit
>
At the moment, I am afraid so. I am considering whether I should
enhance PageKite to allow dynamic allocation of ports on the
front-end, but there hasn't been much demand for that so far and it
could complicate things quite a bit.
I am very surprised if the App Inventor port number is not at all
configurable, are you sure you cannot change it?
Hmm..It would be good to have it, but its already so awesome. Can't ask
for more!
>
> I am very surprised if the App Inventor port number is not at all
> configurable, are you sure you cannot change it?
Well, yeah right now, I am speculating that since they are just shipping
JARs (as they are in a transition state) they have kept it that way. It
was just a personal project to get it up and running. But, I shall post
a query on that list and see if that can be changed now.
Thanks much.
-Amit
>