Accessing Fuseki server outside local network.

[Lewis John Mcgibbney <le...@gmail.com>]

Hi All,
Ideally, I would like to run Fuseki inside Tomcat (I am therefore
monitoring JENA-201 and also offering to put time into getting HTML pages
supported in there) so that I can access my web app outside of local
network.
However this made me think that it would be strange if this were not
already possible.
I start Jetty on localhost:3030 but I am not able to access it from an
external (to localhost) client.
Can someone point me in the right direction here to access the Fuseki
instance on localhost:3030 from my mobile 3G network for example?
Thank you very much in advance.
Best
Lewis

-- 
*Lewis*

Re: Accessing Fuseki server outside local network.

[Lewis John Mcgibbney <le...@gmail.com>]

thanks Andy
Lewis

On Tuesday, August 27, 2013, Andy Seaborne <an...@apache.org> wrote:
> It can certainly be accessed directly - I seem to spend my time stopping
that!
>
> Port 3030 may well be bloked by a firefall somewhere.
>
> We tend to run it behind httpd (or equiv in nginx).
>
> e.g.
>
> <VirtualHost *:80>
>   ServerName www.sparql.org
>   ServerAlias sparql.org
>   ProxyRequests off
>   <Proxy *>
>     Order deny,allow
>     Allow from all
>   </Proxy>
>   ProxyPass / http://127.0.0.1:3030/ max=4
>   ProxyPassReverse / http://127.0.0.1:3030/
>   ProxyPreserveHost On
> </VirtualHost>
>
> You can start it on a different port using --port
>
>         Andy
>
> On 27/08/13 00:15, Lewis John Mcgibbney wrote:
>>
>> Hi Rob,
>> Thank you so much for this. Great.
>> Best
>> Lewis
>>
>>
>> On Mon, Aug 26, 2013 at 3:30 PM, Rob Vesse <rv...@yarcdata.com> wrote:
>>
>>> Lewis
>>>
>>> It will depend heavily on the configuration of the system that you run
the
>>> Fuseki instance on around both its host name and its firewall
>>>
>>> Firstly Fuseki by default binds to the given port (default 3030) on all
>>> hosts, so from your local machine both localhost:3030 and hostname:3030
>>> should work
>>>
>>> As far as accessing outside your machine that is going to be driven by
the
>>> hosts firewall configuration.  A standard firewall configuration in most
>>> host OSes should not permit port 3030 to be accessible from outside the
>>> machine.  You will need to modify your firewall configuration on your
host
>>> to allow inbound TCP/IP traffic on port 3030
>>>
>>> If your host needs to be accessible from beyond the local network the
you
>>> may need to look at changing firewall configuration on your network
>>> hub/router/switch to allow inbound connections on this port from outside
>>> of the network and possibly to enable port forwarding to from the public
>>> IP of your hub/router/switch to your internal IP if the server does not
>>> have a public IP address.
>>>
>>> On the client side you should just be able to access hostname:3030
unless
>>> your client side firewall has rules on outgoing traffic (which most
>>> typically won't) though if after allowing inbound connections on the
>>> server you have problems accessing from some (but not all clients) then
>>> this would be the next thing to investigate.
>>>
>>> Hope this helps, apologies for being low on specifics but firewall
>>> configuration utilities vary widely between OS and even more so when you
>>> get to the network router/switch/hub level.
>>>
>>> Rob
>>>
>>>
>>> On 8/26/13 3:22 PM, "Lewis John Mcgibbney" <le...@gmail.com>
>>> wrote:
>>>
>>>> Hi All,
>>>> Ideally, I would like to run Fuseki inside Tomcat (I am therefore
>>>> monitoring JENA-201 and also offering to put time into getting HTML
pages
>>>> supported in there) so that I can access my web app outside of local
>>>> network.
>>>> However this made me think that it would be strange if this were not
>>>> already possible.
>>>> I start Jetty on localhost:3030 but I am not able to access it from an
>>>> external (to localhost) client.
>>>> Can someone point me in the right direction here to access the Fuseki
>>>> instance on localhost:3030 from my mobile 3G network for example?
>>>> Thank you very much in advance.
>>>> Best
>>>> Lewis
>>>>
>>>> --
>>>> *Lewis*
>>>
>>>
>>
>>
>
>

-- 
*Lewis*

Re: Accessing Fuseki server outside local network.

[Andy Seaborne <an...@apache.org>]

It can certainly be accessed directly - I seem to spend my time stopping 
that!

Port 3030 may well be bloked by a firefall somewhere.

We tend to run it behind httpd (or equiv in nginx).

e.g.

<VirtualHost *:80>
   ServerName www.sparql.org
   ServerAlias sparql.org
   ProxyRequests off
   <Proxy *>
     Order deny,allow
     Allow from all
   </Proxy>
   ProxyPass / http://127.0.0.1:3030/ max=4
   ProxyPassReverse / http://127.0.0.1:3030/
   ProxyPreserveHost On
</VirtualHost>

You can start it on a different port using --port

	Andy

On 27/08/13 00:15, Lewis John Mcgibbney wrote:
> Hi Rob,
> Thank you so much for this. Great.
> Best
> Lewis
>
>
> On Mon, Aug 26, 2013 at 3:30 PM, Rob Vesse <rv...@yarcdata.com> wrote:
>
>> Lewis
>>
>> It will depend heavily on the configuration of the system that you run the
>> Fuseki instance on around both its host name and its firewall
>>
>> Firstly Fuseki by default binds to the given port (default 3030) on all
>> hosts, so from your local machine both localhost:3030 and hostname:3030
>> should work
>>
>> As far as accessing outside your machine that is going to be driven by the
>> hosts firewall configuration.  A standard firewall configuration in most
>> host OSes should not permit port 3030 to be accessible from outside the
>> machine.  You will need to modify your firewall configuration on your host
>> to allow inbound TCP/IP traffic on port 3030
>>
>> If your host needs to be accessible from beyond the local network the you
>> may need to look at changing firewall configuration on your network
>> hub/router/switch to allow inbound connections on this port from outside
>> of the network and possibly to enable port forwarding to from the public
>> IP of your hub/router/switch to your internal IP if the server does not
>> have a public IP address.
>>
>> On the client side you should just be able to access hostname:3030 unless
>> your client side firewall has rules on outgoing traffic (which most
>> typically won't) though if after allowing inbound connections on the
>> server you have problems accessing from some (but not all clients) then
>> this would be the next thing to investigate.
>>
>> Hope this helps, apologies for being low on specifics but firewall
>> configuration utilities vary widely between OS and even more so when you
>> get to the network router/switch/hub level.
>>
>> Rob
>>
>>
>> On 8/26/13 3:22 PM, "Lewis John Mcgibbney" <le...@gmail.com>
>> wrote:
>>
>>> Hi All,
>>> Ideally, I would like to run Fuseki inside Tomcat (I am therefore
>>> monitoring JENA-201 and also offering to put time into getting HTML pages
>>> supported in there) so that I can access my web app outside of local
>>> network.
>>> However this made me think that it would be strange if this were not
>>> already possible.
>>> I start Jetty on localhost:3030 but I am not able to access it from an
>>> external (to localhost) client.
>>> Can someone point me in the right direction here to access the Fuseki
>>> instance on localhost:3030 from my mobile 3G network for example?
>>> Thank you very much in advance.
>>> Best
>>> Lewis
>>>
>>> --
>>> *Lewis*
>>
>>
>
>

Re: Accessing Fuseki server outside local network.

[Lewis John Mcgibbney <le...@gmail.com>]

Hi Rob,
Thank you so much for this. Great.
Best
Lewis


On Mon, Aug 26, 2013 at 3:30 PM, Rob Vesse <rv...@yarcdata.com> wrote:

> Lewis
>
> It will depend heavily on the configuration of the system that you run the
> Fuseki instance on around both its host name and its firewall
>
> Firstly Fuseki by default binds to the given port (default 3030) on all
> hosts, so from your local machine both localhost:3030 and hostname:3030
> should work
>
> As far as accessing outside your machine that is going to be driven by the
> hosts firewall configuration.  A standard firewall configuration in most
> host OSes should not permit port 3030 to be accessible from outside the
> machine.  You will need to modify your firewall configuration on your host
> to allow inbound TCP/IP traffic on port 3030
>
> If your host needs to be accessible from beyond the local network the you
> may need to look at changing firewall configuration on your network
> hub/router/switch to allow inbound connections on this port from outside
> of the network and possibly to enable port forwarding to from the public
> IP of your hub/router/switch to your internal IP if the server does not
> have a public IP address.
>
> On the client side you should just be able to access hostname:3030 unless
> your client side firewall has rules on outgoing traffic (which most
> typically won't) though if after allowing inbound connections on the
> server you have problems accessing from some (but not all clients) then
> this would be the next thing to investigate.
>
> Hope this helps, apologies for being low on specifics but firewall
> configuration utilities vary widely between OS and even more so when you
> get to the network router/switch/hub level.
>
> Rob
>
>
> On 8/26/13 3:22 PM, "Lewis John Mcgibbney" <le...@gmail.com>
> wrote:
>
> >Hi All,
> >Ideally, I would like to run Fuseki inside Tomcat (I am therefore
> >monitoring JENA-201 and also offering to put time into getting HTML pages
> >supported in there) so that I can access my web app outside of local
> >network.
> >However this made me think that it would be strange if this were not
> >already possible.
> >I start Jetty on localhost:3030 but I am not able to access it from an
> >external (to localhost) client.
> >Can someone point me in the right direction here to access the Fuseki
> >instance on localhost:3030 from my mobile 3G network for example?
> >Thank you very much in advance.
> >Best
> >Lewis
> >
> >--
> >*Lewis*
>
>


-- 
*Lewis*

Re: Accessing Fuseki server outside local network.

[Rob Vesse <rv...@yarcdata.com>]

Lewis

It will depend heavily on the configuration of the system that you run the
Fuseki instance on around both its host name and its firewall

Firstly Fuseki by default binds to the given port (default 3030) on all
hosts, so from your local machine both localhost:3030 and hostname:3030
should work

As far as accessing outside your machine that is going to be driven by the
hosts firewall configuration.  A standard firewall configuration in most
host OSes should not permit port 3030 to be accessible from outside the
machine.  You will need to modify your firewall configuration on your host
to allow inbound TCP/IP traffic on port 3030

If your host needs to be accessible from beyond the local network the you
may need to look at changing firewall configuration on your network
hub/router/switch to allow inbound connections on this port from outside
of the network and possibly to enable port forwarding to from the public
IP of your hub/router/switch to your internal IP if the server does not
have a public IP address.

On the client side you should just be able to access hostname:3030 unless
your client side firewall has rules on outgoing traffic (which most
typically won't) though if after allowing inbound connections on the
server you have problems accessing from some (but not all clients) then
this would be the next thing to investigate.

Hope this helps, apologies for being low on specifics but firewall
configuration utilities vary widely between OS and even more so when you
get to the network router/switch/hub level.

Rob


On 8/26/13 3:22 PM, "Lewis John Mcgibbney" <le...@gmail.com>
wrote:

>Hi All,
>Ideally, I would like to run Fuseki inside Tomcat (I am therefore
>monitoring JENA-201 and also offering to put time into getting HTML pages
>supported in there) so that I can access my web app outside of local
>network.
>However this made me think that it would be strange if this were not
>already possible.
>I start Jetty on localhost:3030 but I am not able to access it from an
>external (to localhost) client.
>Can someone point me in the right direction here to access the Fuseki
>instance on localhost:3030 from my mobile 3G network for example?
>Thank you very much in advance.
>Best
>Lewis
>
>-- 
>*Lewis*