[SOGo] Re: Blank page after login on new 1.3.18 install?
*bump*
No suggestions?
Thanks,
//Mike
On 24/09/12 01:42, Michael Gratton wrote:
>
> Hi,
>
> A new installation of SOGo 1.3.18 on Ubuntu 12.04 is giving a 404
> "object not found: SOGo => testuser" error after logging in.
>
> The login page's URL is <http://calendar.domainname.com/SOGo>, and after
> logging in as "testuser" the browser is redirected to
> <http://calendar.domainname.com/SOGo/testuser>, which causes the 404.
>
> I believe my x-webobjects-server-url header is being set correctly, my
> Apache proxy config section looks like:
>
> http://127.0.0.1:2/SOGo>
> RequestHeader set "x-webobjects-server-port" "80"
> RequestHeader set "x-webobjects-server-name" "calendar.domainname.com"
> RequestHeader set "x-webobjects-server-url"
> "http://calendar.domainname.com";
> RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
> RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
> #RequestHeader set "x-webobjects-remote-host" "%{REMOTE_HOST}e"
> env=REMOTE_HOST
>
> ...
>
> Any suggestions welcome!
> //Mike
>
--
Michael Gratton
Quuxo Software <http://web.quuxo.com/>
signature.asc
Description: OpenPGP digital signature
[SOGo] Blank page after login on new 1.3.18 install?
Hi,
A new installation of SOGo 1.3.18 on Ubuntu 12.04 is giving a 404
"object not found: SOGo => testuser" error after logging in.
The login page's URL is <http://calendar.domainname.com/SOGo>, and after
logging in as "testuser" the browser is redirected to
<http://calendar.domainname.com/SOGo/testuser>, which causes the 404.
I believe my x-webobjects-server-url header is being set correctly, my
Apache proxy config section looks like:
http://127.0.0.1:2/SOGo>
RequestHeader set "x-webobjects-server-port" "80"
RequestHeader set "x-webobjects-server-name" "calendar.domainname.com"
RequestHeader set "x-webobjects-server-url"
"http://calendar.domainname.com";
RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
#RequestHeader set "x-webobjects-remote-host" "%{REMOTE_HOST}e"
env=REMOTE_HOST
...
Any suggestions welcome!
//Mike
--
Michael Gratton
Quuxo Software <http://web.quuxo.com/>
signature.asc
Description: OpenPGP digital signature
[SOGo] make gnustep-make a Build-Depends?
Hey, Is there any reason why the SOGo debs lists gnustep-make as a Depends? Doing so causes gobjc to be installed, which in turn also pulls in gcc. I really dislike having one compiler installed on my servers, let alone two — it's a great way for attackers to exploit a remote security vulnerability. Should gnustep-make be a Build-Depends instead? Cheers! //Mike -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
Re: [SOGo] SOGo v2 architecture
On 09/09/12 00:05, CF Studelec wrote: > Thank you Francis, this document is a must have. > Along these lines, is there documentation on the web site of what improvements 2.0 has beyond 1.3 (aside from OpenChange/Outlook integration)? I have looked, but not found anything. I am about to commission a new machine running SOGo and need to decide if the pain of deploying a RC candidate of 2.0 is going to be worth while, or commit to continue using 1.3 on it for the next four years. Thanks, //Mike -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
Re: [SOGo] Re: cannot create new contacts or events using web UI
Hi,
Thanks for the suggestions.
Le 13/03/12 10:16, Ludovic Marcotte a écrit :
> Instead of :
>
> RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
>
> use:
>
> RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e
> env=REMOTE_HOST
I tried that (and with quotes around the value) and had some weird
results when requesting "/", but in any case it didn't seem to fix the
problem.
What does the x-webobjects-remote-host header do? If anything, it seems
like it would just inform SOGo of the client's IP address, but I doubt
that it would affect the server's address as generated in the HTML,
which is the problem.
> Also:
>
> BalancerMember http://127.0.0.1:2 retry=1 max=1 timeout=120
> BalancerMember http://127.0.0.1:20001 retry=1 max=1 timeout=120
>
> is most likely wrong. I don't recall if v1.3.6 had the master process
> code which is dispatching requests to child processes but you could
> easily verify this by checking if port 20001 is open.
Thanks, I'll have a a look into this (and the former a bit more) out of
business hours when I can muck around with it more.
//Mike
--
Michael Gratton
Quuxo Software <http://web.quuxo.com/>
signature.asc
Description: OpenPGP digital signature
Re: [SOGo] Re: cannot create new contacts or events using web UI
Le 13/03/12 09:55, Ludovic Marcotte a écrit : > On 12/03/12 18:46, Michael Gratton wrote: >> Well, it is an old installation, but this problem has persisted across a >> number of versions of SOGo now. Although we don't really use the web >> interface, it is a rather core function that is broken, so I doubt it's >> a bug and that upgrading will help. > Share the part of your sogo.log file when you try to create an event or > a contact. > There is no SOGo log entry, because on clicking the Save button for the event the browser tries to submit to localhost rather than to the SOGo installation's host. I.e. The browser sends the request to: http://127.0.0.1:2/SOGo/[snip] Rather than: http://collab.internal.xyz.com/[snip] -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
Re: [SOGo] Re: cannot create new contacts or events using web UI
Le 12/03/12 21:09, Christian Mack a écrit : > > I hat a similar problem after upgrading. > The solution was to clear the browser cache. > > But I don't think this is related to your problem, as you obviously try > to set up a fresh SOGo. Well, it is an old installation, but this problem has persisted across a number of versions of SOGo now. Although we don't really use the web interface, it is a rather core function that is broken, so I doubt it's a bug and that upgrading will help. More likely it's a configuration issue, but after consulting the documentation it seems like the instance is configured fine, which is why I was hoping someone on the list might have some advice. Cheers, //Mike -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
[SOGo] Re: cannot create new contacts or events using web UI
No-one has any advice on this? Message original Sujet: cannot create new contacts or events using web UI Date : Thu, 08 Mar 2012 13:53:19 +1100 De : Michael Gratton Organisation : Quuxo Software Pour : users@sogo.nu Hi, Using sogo-1.3.6-1.el5, I cannot create a new address book contacts or calendar events using the web interface. When hitting save on either the new contact or the new event, the result is a generic browser connection error page, since the form is attempting to submit to <http://127.0.0.1:2/SOGo/[snip]> rather than the correct address of the calendar server, i.e. <http://collab.internal.xyz.com/[snip]> Everything else seems to work fine. I am using Apache as a front end on the calendar server, and have the following proxy config: BalancerMember http://127.0.0.1:2 retry=1 max=1 timeout=120 BalancerMember http://127.0.0.1:20001 retry=1 max=1 timeout=120 ProxySet lbmethod=byrequests maxattempts=1 Order deny,allow allow from all RequestHeader set "x-webobjects-server-port" "80" RequestHeader set "x-webobjects-server-name" "collab.internal.xyz.com" RequestHeader set "x-webobjects-server-url" "http://collab.internal.xyz.com"; RequestHeader set "x-webobjects-remote-host" "127.0.0.1" AddDefaultCharset UTF-8 Any suggestions? -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
[SOGo] cannot create new contacts or events using web UI
Hi, Using sogo-1.3.6-1.el5, I cannot create a new address book contacts or calendar events using the web interface. When hitting save on either the new contact or the new event, the result is a generic browser connection error page, since the form is attempting to submit to <http://127.0.0.1:2/SOGo/[snip]> rather than the correct address of the calendar server, i.e. <http://collab.internal.xyz.com/[snip]> Everything else seems to work fine. I am using Apache as a front end on the calendar server, and have the following proxy config: BalancerMember http://127.0.0.1:2 retry=1 max=1 timeout=120 BalancerMember http://127.0.0.1:20001 retry=1 max=1 timeout=120 ProxySet lbmethod=byrequests maxattempts=1 Order deny,allow allow from all RequestHeader set "x-webobjects-server-port" "80" RequestHeader set "x-webobjects-server-name" "collab.internal.xyz.com" RequestHeader set "x-webobjects-server-url" "http://collab.internal.xyz.com"; RequestHeader set "x-webobjects-remote-host" "127.0.0.1" AddDefaultCharset UTF-8 Any suggestions? -- Michael Gratton Quuxo Software <http://web.quuxo.com/> signature.asc Description: OpenPGP digital signature
