I installed the latest galaxy server and started it without any change. The
server stared on port 8080 and the log file looks fine. But when I typed
http://localhost:8080, I got the error Unable to connect. I had worked
with version 2014_08_11 and had no problem at all. What could have been
wrong?
I installed the latest Galaxy (v15.07) and tested with a job. I found my
local environment setup file was not executed. The line of code that
executes the local setup file is
[ -f "config/local_env.sh" ] && . config/local_env.sh
Further looking into the galaxy_xx.sh file shows the current
I recently installed galaxy v16.10 and have set "allow_user_impersonation =
True". However, the impersonation feature seems don't work properly. When I
click "Admin->impersonate a user" and choose the account I want to
impersonate, and the click "impersonate" button. The page shows "you have
login
The impersonation feature in Galaxy v17.09 doesn't work as expected.
After clicking the person to impersonate, the webpage shows "you have now
logged in as xxx, return to home page', where 'xxx' is the name of the
person I want to impersonate. So far so good. But after I click home, and
check the
rue" in the
> galaxy.ini file?
>
>
> Do you encounter this problem, for the first time, i.e did it work before
> using (v17.05 or earlier) and you only have the issues after upgrading?
>
> What database do you use?
>
> Do you use external authentication?
>
>
&g
I just installed Galaxy V18.01. I got an error when clicking 'View all
histories' in the history tool bar
The error says 'The requested URL /api/histories was not found on this
server'.
Is there anyone experiencing the same problem?
Ping
> wrote:
> You’ll probably get a more informative error message if you check the
> logs.
>
> Sent from my iPhone
>
> > On 15. May 2018, at 17:45, Ping Luo <luop0...@gmail.com> wrote:
> >
> > I just installed Galaxy V18.01. I got an error when clicking 'View
ll take a quick look, this should be an easy fix.
>
> On Tue, May 15, 2018 at 12:25 PM Ping Luo <luop0...@gmail.com> wrote:
>
>> The Galaxy log file shows:
>> [15/May/2018:11:20:44 -0500] "GET /template/api/webhooks HTTP/1.1" 200 -
>> "https://xxx.xxx.
gt;
>
> Does it work with a fresh installation ( v17.09) staring with an empty
> PostgrSQL database?
>
>
> Hans-Rudolf
>
> On 12/19/2017 03:41 PM, Ping Luo wrote:
>
>> Hans-Rudolf,
>>
>> Yes, I have set the flag to be true
>>
>> # A
I configured URL prefix in galaxy 18.09. It has problems of resolving some
of the links, including:
workflow
visualize -> create visualization
shared data -> workflows
shared data -> visualizations
I will use workflow as an example to illustrate what happens. When the
mouse
I am trying to configure Galaxy v18.09 wtih sub-uri. In prior 18.01, I use
this configuration in conjunction with Apache rewrite rules and it works
well:
[filter:proxy-prefix]
use = egg:PasteDeploy#prefix
prefix = /msgalaxy
[app:main]
filter-with = proxy-prefix
cookie_path = '/galaxy'
In
anchester
> B.1083 Michael Smith Bldg Tel: (0161) 2751482
>
> --
> *From:* galaxy-dev [galaxy-dev-boun...@lists.galaxyproject.org] on behalf
> of Ping Luo [luop0...@gmail.com]
> *Sent:* Wednesday, December 12, 2018 6:35 AM
> *To:* galaxy-dev
&
Peter,
I just figured out how to fix it. In galaxy.yml, I changed HTTP_REMOTE_USER
to REMOTE_USER, and now it works. My next thing is to test the sub-uri.
Thanks,
Ping
On Fri, Dec 14, 2018 at 11:02 AM Ping Luo wrote:
> Peter,
>
> I have been using the default http protocol for t
;
> This appears to fix the links to "Workflows" and "Visualisations" in the
> masthead of the main page.
>
> HTH
>
> Best wishes
>
> Peter
>
> --
> Peter Briggs peter.bri...@manchester.ac.uk
> Bioinformatics Core Facility University of Manches
14 matches
Mail list logo
