Author Topic: Accessing opengoo locally and remotely  (Read 6247 times)

Capitan

  • Jr. Member
  • **
  • Posts: 63
    • View Profile
Accessing opengoo locally and remotely
« on: December 09, 2008, 10:59:42 pm »
I'm having a problem in that I prefer to use http://localhost/? when I access it locally, but then I have a problem accessing through the internet.

How do I configure opengoo to work with localhost and over the internet correctly?


ignacio

  • Hero Member
  • *****
  • Posts: 1703
    • View Profile
Re: Accessing opengoo locally and remotely
« Reply #1 on: December 10, 2008, 08:55:25 am »
If I understand correctly, you installed OpenGoo on some PC and want to be able to access it from that same PC and from outside of the PC (either by a domain name or by its IP address), right?

Then, you should be able to access OpenGoo locally as well as externally by using that same domain name or IP address. Just be sure that the value for ROOT_URL in config/config.php is the domain name or IP address.

If you still want to use 'http://localhost'  for some reason when accessing it locally you could set the ROOT_URL value to the path after 'localhost'. Example, if you installed opengoo on 'http://localhost/opengoo' then you would set the ROOT_URL to '/opengoo'. This would allow you to access it through any domain name or IP address. But, when URL's are generated in OpenGoo, they'll start with '/opengoo' instead of 'http://something/opengoo'. This is specially annoying when you receive notification emails that contain URLs from OpenGoo, because your email client won't recognize '/opengoo' as an URL and so you can't just click it to access OpenGoo (and even if you could click it, without the 'http://server' part it wouldn't take you anywhere).

Cheers.

Capitan

  • Jr. Member
  • **
  • Posts: 63
    • View Profile
Re: Accessing opengoo locally and remotely
« Reply #2 on: December 10, 2008, 05:00:04 pm »
Thanks. 

This is a problem because I want to access it locally and remotely.  However, if I set the public ip as root_url, then to access it remotely I must type in the public address, which means it is slower and also less secure.

I was wondering the best way to make it accessible via localhost and via the internet.

Pontiac

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: Accessing opengoo locally and remotely
« Reply #3 on: December 13, 2008, 02:32:03 pm »
What I did was install a VPN server, open up ports on my router to point the server.  This allowed any Win2K/XP/Vista/Linux machine I may be using to connect to my home machine so that I may use OpenGoo.  This creates a big extra layer of security so that OpenGoo just isn't flapping out on the internet. ;)

If you're not all that interested in setting up a VPN server as I did, another alternative would be using a service called Hamachi.  You can find it at http://www.logmein.com.  Its free for private use.

In both cases, you have to configure OpenGoo to either use the servers static IP, or Hamachis IP.

If theres enough interest, I may be convinced to come up with a walk through on setting up either Hamachi or a VPN server.

martino87r

  • Newbie
  • *
  • Posts: 29
    • View Profile
    • Email
Re: Accessing opengoo locally and remotely
« Reply #4 on: December 14, 2008, 08:49:52 pm »
Well the VPN is not so a great solution...
Of course you get encoded data stream over the internet, but it will be possible for any worm to affect directly the host LAN (in case of a host-to-lan VPN)...
I will go for an HTTPS solution, then maybe it's a little bit more secure than building up a VPN (instead of this proprietary vpn you can use OpenVPN)

Capitan

  • Jr. Member
  • **
  • Posts: 63
    • View Profile
Re: Accessing opengoo locally and remotely
« Reply #5 on: December 17, 2008, 02:43:18 pm »
Im already using https, but the problem is that opengoo forces you to hard code the public url.   Can't that be avoided?

Pontiac

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: Accessing opengoo locally and remotely
« Reply #6 on: December 26, 2008, 10:49:30 am »
Well the VPN is not so a great solution...
Of course you get encoded data stream over the internet, but it will be possible for any worm to affect directly the host LAN (in case of a host-to-lan VPN)...
I will go for an HTTPS solution, then maybe it's a little bit more secure than building up a VPN (instead of this proprietary vpn you can use OpenVPN)

If you want to start talking about trojans, key loggers, and viruses, then is any data safe, regardless of HTTPS/VPN/Security?

VPN is an additional layer of security.  Its not the end-all or say-all of methods, its just in my case the easiest thing to do for OpenVPN as you can only HAVE one home URL address.