Unable to get server to listen for xmlrpcs

Bug #936831 reported by Alan Lord
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Won't Fix
Wishlist
Unassigned

Bug Description

On a recent nightly build of openerp-server-6.1 (20120216-200739) I am unable to get the server to listen or bind to port 8071 according to nmap and I am unable to connect using the trunk GTK client.

There are no errors reported in the log file (tried with debug and debug_rpc levels). The key and cert are fine. I have used this configuration before on OpenERP 6.0.3 successfully.

[options]
without_demo = False
smtp_port = 25
db_template = template0
db_password = False
xmlrpcs = True
xmlrpcs_interface =
syslog = False
logrotate = True
xmlrpcs_port = 8071
test_report_directory = False
list_db = True
timezone = False
xmlrpc_interface =
test_file = False
cache_timeout = 100000
smtp_password = False
secure_pkey_file = /etc/ssl/openerp/server.key
xmlrpc_port = 8069
log_level = info
xmlrpc = True
test_disable = False
admin_passwd = admin123
assert_exit_level = error
smtp_server = localhost
static_http_url_prefix = None
unaccent = False
test_commit = False
proxy_mode = False
demo = {}
db_host = False
login_message = False
import_partial =
pidfile = None
db_maxconn = 64
osv_memory_count_limit = False
reportgz = False
osv_memory_age_limit = 1.0
netrpc_port = 8070
db_port = False
virtual_memory_reset = 671088640
db_name = False
debug_mode = False
netrpc = True
secure_cert_file = /etc/ssl/openerp/server.crt
logfile = /var/log/openerp/openerp-server.log
csv_internal_sep = ,
virtual_memory_limit = 805306368
pg_path = None
static_http_enable = False
cpu_time_limit = 60
translate_modules = ['all']
smtp_ssl = False
server_wide_modules = None
netrpc_interface =
smtp_user = False
log_handler = [':INFO']
db_user = openerp
dbfilter = .*
max_cron_threads = 4
email_from = False
addons_path = /opt/openerp/server/openerp/addons
static_http_document_root = None

Revision history for this message
Alan Lord (theopensourcerer) wrote :

OK - Further testing done. It would seem that xmlrpcs isn't really working at all in 6.1. However, it one uses a reverse proxy to terminate ssl (apache or nginx for example) on port 8069, then the GTK client will successfully connect using xmlrpcs to port 443 of the web server.

In my opinion then, the configuration switches should be removed from the configuration file and documentation provided to explain the change.

Revision history for this message
Vincent Renaville@camptocamp (vrenaville-c2c) wrote :

Hello,

According to OpenERP team.
SSL configuration in openerp-server.cfg is useless and should be remove from config file.

For 6.1 you need to use an Nginx or Apache as a proxy with SSL .

Hope this help,

Kind regards,

Vincent

Revision history for this message
Alan Lord (theopensourcerer) wrote :

@Vincent,

Our replies crossed, I worked it out just as you commented.

I agree, the configuration options should be removed. It would have saved me a lot of wasted time.

Revision history for this message
Vo Minh Thu (thu) wrote :

Hi,

We have indeed removed HTTPS support from the server at the same time we changed it to use Wekzeug. It should be straightforward (a couple of lines) to add it back (as Werkzeug directly supports it) if it is really needed.

We have unfortunatly forgotten to remove the corresponding options from the configuration file and command-line parser (this one could qualify as a bug).

The reason we removed it is the following:

The server shipping with Werkzeug is clearly stated as non-production ready (for develoment only). Knowing this, it seems contradictory to let people use it with SSL enabled (you want to use SSL when opening connections to the world, and you want to do that when you're going into production).

Changed in openobject-server:
importance: Undecided → Wishlist
status: New → Won't Fix
Revision history for this message
Alan Lord (theopensourcerer) wrote :

OK - Not sure I completely buy the non-production ready thing... What is supposed to happen when 6.1 gets released then? Will there be documentation explaining a way to provide "production ready" web-access?

But anyway, do you want me to raise a new bug for the irrelevant config file switches?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.