This question has been flagged
1 Reply
8862 Views

I have set up an Odoo 8 server with three databases.  I have attempted to invite new users to one of the databases, but they get a 404 when they try to follow the link in the invitation email.  The problem appears to be that Odoo is relying on a cookie or something local to the browser to know what database to access.  I figured out a workaround after examining the server access logs excerpted below.  Notice that the second attempt worked, and all the others failed.  Every access attempt corresonding to a "INFO None werkzeug" log entry failed, while the one that generated "INFO ART werkzeug" succeeded.  ART is the name of the database we're after, as you can see from the db=ART node of the URL.

2014-10-17 16:51:05,067 720 INFO None werkzeug: 127.0.0.1 - - [17/Oct/2014 16:51:05] "GET /web/reset_password?token=7ddLQc45Pmt6awpj2Pvj&db=ART HTTP/1.1" 404 -

2014-10-17 16:52:14,655 720 INFO ART werkzeug: 127.0.0.1 - - [17/Oct/2014 16:52:14] "GET /web/reset_password?token=7ddLQc45Pmt6awpj2Pvj&db=ART HTTP/1.1" 200 -
2014-10-17 16:53:31,292 720 INFO None werkzeug: 127.0.0.1 - - [17/Oct/2014 16:53:31] "GET /web/reset_password?token=7ddLQc45Pmt6awpj2Pvj&db=ART HTTP/1.1" 404 -
2014-10-17 16:55:52,536 720 INFO None werkzeug: 127.0.0.1 - - [17/Oct/2014 16:55:52] "GET /web/reset_password?token=7ddLQc45Pmt6awpj2Pvj&db=ART HTTP/1.1" 404 -
2014-10-17 16:56:16,001 720 INFO None werkzeug: 127.0.0.1 - - [17/Oct/2014 16:56:16] "GET /web/reset_password?token=7ddLQc45Pmt6awpj2Pvj&db=ART HTTP/1.1" 404 -

To work around the problem, I instructed the users that before attempting to follow the link in the invitation email, they should first visit the equivalent of http://odooserver.mycompany.com/web/database/selector and select ART (or whatever appropriate database).  Then, without trying to log in, return to their email invitation and follow the invitation link.

This is obviously a bug that occurrs when there are multiple databases (perhaps only when inviting someone to a database that was not created first?).

Avatar
Discard

I'm running into the same problem. It would be great to have a real solution rather than the "web/database/selector" workaround.

Author Best Answer

I'm no longer experiencing this problem with invitation emails because of a change I made in the way I'm having users access the database to which they are invited.  My solution may or may not be appropriate for your environment.  I'm using a unique URL for each database.  After reviewing every post I could find on how to do that, I had to create and document the procedure myself, because I ran into problems with every method I found.  My explanatino of how to use to configure Apache and DNS and/or the server's hosts table in order to correlate a domain/subdomain name with one specific database can be found at http://www.inlinetechnology.com/odoo-notes/.  This gets around the problem discussed above, because there's no longer any possible ambiguity about which database the browser is looking for.

Avatar
Discard

Thanks Tony! I will try out your solution. It looks to be exactly what I need.

Tony, this worked great. I am using nginx in front of Odoo and your concept worked perfectly. Thanks!

Glad it worked out for you, Dan.  I’d appreciate your up-voting my answer on the forum, so I can get enough karma to be able to ask my own questions.  Kind of silly how the karma system works.  I found myself unable to ask a question because I had bothered to answer a couple.

 

Tony Felice

Office: 216-221-4600 x199

Cell: 216-375-3250

Skype: tony_felice

Fax: 216-287-7085

vCard: Click to download

 

<img border="0" width="212" height="63" id="Picture_x0020_1" src="cid:image003.jpg@01D004CE.E26AF9A0" alt="inline logo with tagline_email 2">

 

From: Dan [mailto:ddeighton-openerp-aplura-com@mail.odoo.com]
Sent: Thursday, November 20, 2014 1:46 PM
To: Tony Felice
Subject: Re: False

 

Tony, this worked great. I am using nginx in front of Odoo and your concept worked perfectly. Thanks!

--
Dan
Sent by OpenERP S.A. using Odoo about Forum Post False