Hi, I'm having trouble setting up the apache to redirect my local running galaxy which runs on localhost:8080 I would like that people could have access inside the lab knowing my local ip address. I read plenty of tutorials, can anyone help setting it up on Ubuntu? The files I have to modify are located at: /etc/apache2/sites-available/ 000-default.conf and default-ssl.config ? apache is up and running. Cheers Jochen
Hi Jochen, I presume you looked at this already: https://wiki.galaxyproject.org/Admin/Config/ApacheProxy Those instructions work for Ubuntu as well. What do your Apache2 error logs says (in /var/log/apache2/)? And what have you tried in your configuration files? And are you trying to forward port 80 to 8080, 443 to 8080 or something else? Ray On Fri, Sep 2, 2016 at 5:53 AM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
Hi,
I'm having trouble setting up the apache to redirect my local running galaxy which runs on localhost:8080 I would like that people could have access inside the lab knowing my local ip address. I read plenty of tutorials, can anyone help setting it up on Ubuntu? The files I have to modify are located at: /etc/apache2/sites-available/ 000-default.conf and default-ssl.config ?
apache is up and running.
Cheers Jochen ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi Ray, yes exactly. So my problem is that I have no idea where to copy those settings. I have tutorial how it works on Centos but the file structure is different on Ubuntu. So I have my galaxy instance running on localhost:8080 (can also be moved to something else). If I run localhost or my local ip in a browser I see the apache also from a different PC in my network. So my idea is to redirect the apache or galaxy to my IP so that everyone in the network can see and use it (ssl encrypted if possible) Cheers Jochen On 02.09.2016 06:02, Raymond Wan wrote:
Hi Jochen,
I presume you looked at this already:
https://wiki.galaxyproject.org/Admin/Config/ApacheProxy
Those instructions work for Ubuntu as well. What do your Apache2 error logs says (in /var/log/apache2/)? And what have you tried in your configuration files?
And are you trying to forward port 80 to 8080, 443 to 8080 or something else?
Ray
On Fri, Sep 2, 2016 at 5:53 AM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
Hi,
I'm having trouble setting up the apache to redirect my local running galaxy which runs on localhost:8080 I would like that people could have access inside the lab knowing my local ip address. I read plenty of tutorials, can anyone help setting it up on Ubuntu? The files I have to modify are located at: /etc/apache2/sites-available/ 000-default.conf and default-ssl.config ?
apache is up and running.
Cheers Jochen ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi Jochen, On Fri, Sep 2, 2016 at 8:32 PM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
yes exactly. So my problem is that I have no idea where to copy those settings. I have tutorial how it works on Centos but the file structure is different on Ubuntu.
Slightly different, but not too different. If it's Apache then the general format of its configuration files is probably the same. Just the path and how to restart the web server will differ. I tried setting it up before but that was a long time ago. But if not me, perhaps someone else can help you if you post (a) what you have so far in the configuration files and (b) what kind of errors you're getting in your error logs.
So I have my galaxy instance running on localhost:8080 (can also be moved to something else). If I run localhost or my local ip in a browser I see the apache also from a different PC in my network. So my idea is to redirect the apache or galaxy to my IP so that everyone in the network can see and use it (ssl encrypted if possible)
I would ignore SSL for the moment. You should probably break up your problem into smaller problems. Try editing 000-default.conf. Then throw the RewriteRules in the aforementioned web page into that. I think that page is actually quite self-explanatory. For example, this rule: RewriteRule ^(.*) http://localhost:8080$1 [P] would rewrite the URLs so that anyone accessing your site on port 80 would then get sent to port 8080. If it's another server, then it would then be something like this: RewriteRule ^(.*) http://www.example.com:8080$1 [P] Of course, you can change that to https, etc. but, again, move step by step and see if you can get port 80 on localhost redirected to port 8080 on localhost first. Ray
Hi Ray, I added two lines to the following file: /etc/apache2/sites-available/000-default.conf it now looks like this: <VirtualHost *:80> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com ServerAdmin webmaster@localhost DocumentRoot /var/www/html # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf RewriteEngine on RewriteRule ^(.*) http://localhost:8080$1 [P] </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet but it does not have any effect. Here the error.log but there is no error: [Fri Sep 02 15:28:21.677881 2016] [mpm_event:notice] [pid 6627:tid 140049034254208] AH00493: SIGUSR1 received. Doing graceful restart [Fri Sep 02 15:28:21.688069 2016] [proxy_html:notice] [pid 6627:tid 140049034254208] AH01425: I18n support in mod_proxy_html requires mod_xml2enc. Without it, non-ASCII characters in proxied pages are likely to display incorrectly. [Fri Sep 02 15:28:21.689351 2016] [mpm_event:notice] [pid 6627:tid 140049034254208] AH00489: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g-fips configured -- resuming normal operations [Fri Sep 02 15:28:21.689355 2016] [core:notice] [pid 6627:tid 140049034254208] AH00094: Command line: '/usr/sbin/apache2' Cheers Jochen
Hi Jochen, On Sat, Sep 3, 2016 at 2:31 AM, Bick Jochen <jochen.bick@usys.ethz.ch> wrote:
RewriteEngine on RewriteRule ^(.*) http://localhost:8080$1 [P]
...
but it does not have any effect. Here the error.log but there is no error: [Fri Sep 02 15:28:21.677881 2016] [mpm_event:notice] [pid 6627:tid 140049034254208] AH00493: SIGUSR1 received. Doing graceful restart
I presume you've restarted the web server after making this change? Apache's mod_rewrite (the module you are using to achieve the above) has a logging facility, which you might want to read about: http://httpd.apache.org/docs/current/mod/mod_rewrite.html#logging Also, as what you're trying to do isn't specific to Galaxy, you might want to ask your questions on other forums. (i.e., askubuntu, etc.) They may not know what Galaxy is, but if you pose the problem as a redirection from port 80 to 8080 (and you wanted 443, as well?), I think an Apache expert (not me; I have gotten what you're doing working before, but it was a while ago and maybe I was just lucky) may be able to help. Ray
You may need to load the mod_rewrite module. This can be done via: sudo a2enmod rewrite -Will On Mon, Sep 5, 2016 at 7:10 AM, Raymond Wan <rwan.work@gmail.com> wrote:
Hi Jochen,
On Sat, Sep 3, 2016 at 2:31 AM, Bick Jochen <jochen.bick@usys.ethz.ch> wrote:
RewriteEngine on RewriteRule ^(.*) http://localhost:8080$1 [P]
...
but it does not have any effect. Here the error.log but there is no error: [Fri Sep 02 15:28:21.677881 2016] [mpm_event:notice] [pid 6627:tid 140049034254208] AH00493: SIGUSR1 received. Doing graceful restart
I presume you've restarted the web server after making this change?
Apache's mod_rewrite (the module you are using to achieve the above) has a logging facility, which you might want to read about:
http://httpd.apache.org/docs/current/mod/mod_rewrite.html#logging
Also, as what you're trying to do isn't specific to Galaxy, you might want to ask your questions on other forums. (i.e., askubuntu, etc.) They may not know what Galaxy is, but if you pose the problem as a redirection from port 80 to 8080 (and you wanted 443, as well?), I think an Apache expert (not me; I have gotten what you're doing working before, but it was a while ago and maybe I was just lucky) may be able to help.
Ray ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
-- The information contained in this e-mail message or any attachment(s) may be confidential and/or privileged and is intended for use only by the individual(s) to whom this message is addressed. If you are not the intended recipient, any dissemination, distribution, copying, or use is strictly prohibited. If you receive this e-mail message in error, please e-mail the sender at wholtz@lygos.com and destroy this message and remove the transmission from all computer directories (including e-mail servers). Please consider the environment before printing this email.
Hi Will and Ray,
You may need to load the mod_rewrite module. This can be done via: sudo a2enmod rewrite
I will try that. Is this also resetting the modules of apache?
-Will
I presume you've restarted the web server after making this change?
Apache's mod_rewrite (the module you are using to achieve the above) has a logging facility, which you might want to read about:
Yes I did a restart. Maybe I put the code to the wrong position? I think I will also ask somewhere else for help. Cheers Jochen
a2enmod adds an apache module to your list of enabled modules. Previously enabled modules will remain enabled. -Will On Tue, Sep 13, 2016 at 12:10 AM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
Hi Will and Ray,
You may need to load the mod_rewrite module. This can be done via: sudo a2enmod rewrite
I will try that. Is this also resetting the modules of apache?
-Will
I presume you've restarted the web server after making this change?
Apache's mod_rewrite (the module you are using to achieve the above) has a logging facility, which you might want to read about:
Yes I did a restart. Maybe I put the code to the wrong position?
I think I will also ask somewhere else for help.
Cheers Jochen
-- The information contained in this e-mail message or any attachment(s) may be confidential and/or privileged and is intended for use only by the individual(s) to whom this message is addressed. If you are not the intended recipient, any dissemination, distribution, copying, or use is strictly prohibited. If you receive this e-mail message in error, please e-mail the sender at wholtz@lygos.com and destroy this message and remove the transmission from all computer directories (including e-mail servers). Please consider the environment before printing this email.
Jochen, Two quick questions for you: You say you can see the Apache instance from other machines on the network. I assume you are accessing your machine via its local IP address (something like 192.168.1.x); what happens when you try to access Galaxy via http://192.168.1.x:8080? I see you are editing the config file in /etc/apache2/sites-available; have you enabled this site? That is, do you also see the config file in /etc/apache2/sites-enabled? Keith
On Sep 2, 2016, at 5:32 AM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
Hi Ray,
yes exactly. So my problem is that I have no idea where to copy those settings. I have tutorial how it works on Centos but the file structure is different on Ubuntu.
So I have my galaxy instance running on localhost:8080 (can also be moved to something else). If I run localhost or my local ip in a browser I see the apache also from a different PC in my network. So my idea is to redirect the apache or galaxy to my IP so that everyone in the network can see and use it (ssl encrypted if possible)
Cheers Jochen
On 02.09.2016 06:02, Raymond Wan wrote:
Hi Jochen,
I presume you looked at this already:
https://wiki.galaxyproject.org/Admin/Config/ApacheProxy
Those instructions work for Ubuntu as well. What do your Apache2 error logs says (in /var/log/apache2/)? And what have you tried in your configuration files?
And are you trying to forward port 80 to 8080, 443 to 8080 or something else?
Ray
On Fri, Sep 2, 2016 at 5:53 AM, Jochen Bick <jochen.bick@usys.ethz.ch> wrote:
Hi,
I'm having trouble setting up the apache to redirect my local running galaxy which runs on localhost:8080 I would like that people could have access inside the lab knowing my local ip address. I read plenty of tutorials, can anyone help setting it up on Ubuntu? The files I have to modify are located at: /etc/apache2/sites-available/ 000-default.conf and default-ssl.config ?
apache is up and running.
Cheers Jochen ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
------------------------------ Research Associate Department of Computer Science Vassar College Poughkeepsie, NY
Hi Keith,
You say you can see the Apache instance from other machines on the network. I assume you are accessing your machine via its local IP address (something like 192.168.1.x); what happens when you try to access Galaxy via http://192.168.1.x:8080?
Yes I used my local IP and checked it from another PC inside the local network. I just saw the apache running. Changing the to the correct port did not give me access to my running galaxy.
I see you are editing the config file in /etc/apache2/sites-available; have you enabled this site? That is, do you also see the config file in /etc/apache2/sites-enabled?
I have to check again but I think I also saw the sides-enabled. Cheers Jochen
participants (5)
-
Bick Jochen -
Jochen Bick
-
Raymond Wan -
Suderman Keith -
Will Holtz