Open Microscopy Environment

Hi,

So this probably stems from a general ignorance on my part of how servers work in general, but I am having trouble connecting with a remote computer to my OMERO server.

On the computer with the server installed, I can simply go to localhost:8080/webadmin to get to the webadmin login, or alternatively 127.0.0.1:8000/webadmin. It seems from playing around with this that this name/IP works only internally within this computer.

In terms of remote connections, .insight/.importer/.editor can all access the server when the server address is <computer name>.<local network address> (ie, fred.example.edu). However, I simply cannot log into webadmin/webclient with any combination of things I have tried. In other words, putting fred.example.edu into the URL (fred.example.edu/webadmin, or fred.example.edu:8000/webadmin, or a bunch of other combination I've tried, including what I THINK my ip address is for both the server computer and the server itself) will just give me "connection refused."

I'm wondering if something else needs to be installed, separate from the OMERO server installation, to get .web to work? I found this page: http://www.openmicroscopy.org/site/supp ... nstall-web and got a little confused since it wasn't clearly stated when I need Apache + mod_python and when I don't (it seems I need Apache + mod_python only on production servers, since it's not mentioned at all on the non-production servers part, but it's listed as a "Prerequisite" without any indication that it's only a prereq if I choose the production server route...).

Did I not install something I need for the webserver to work for remote connections? Have I just not figured out what the IP is of my OMERO server? How would I find that?

Thanks

Could you please look at the post viewtopic.php?f=5&t=24
I think this might help you to fix the remote connection.

Django application offers development web server what is documented in http://docs.djangoproject.com/en/dev/in ... ent-server but we do not recommend using this server in a production mode. It has not gone through security audits or performance tests. Apache with mod_python is the preferred setup for deploying a Django application on a production server. You can find more information on the Django site http://docs.djangoproject.com/en/1.0/ho ... modpython/.

ah, thanks. that resolved it. i got caught up in the confusion of when i need to do the django thing and when i don't, and when i'm not using the default host (my impression was that i needed to do this change to server.py only when i'm not using the default host, ie the computer omero server is installed on, but apparently i need to do that even with this computer).