Eurotimmy Posted January 9 Share Posted January 9 (edited) ** IMPORTANT NOTE ** For the installation of Odoo 17 I've created a README which has steps I took to get mine up and running The 'PostArgs' in the Docker template need to be deleted (remove the "-i base" command) Update 24 Jan 2024: The website editing part of Odoo 17 was failing / causing an error which rendered the website editor pretty useless I have updated the README and my example odoo.conf file with corrected information on the reverse proxy setup as discussed in this post (below) Update 23 Jan 2024: I have updated the README with another command for 'PostArgs' if you wish to install Odoo17 without any preloaded DEMO data TL;DR - Use this instead "-i base --without-demo=all --stop-after-init" Remember to REMOVE the 'PostArgs' after the initial / first run of the container Edited January 24 by Eurotimmy Updated 'install without demo data' in README Quote Link to comment
menuscreen Posted January 11 Share Posted January 11 Hi, I was trying out the Odoo17 container and I’m unable to get the WebGUI up. The container logs show there’s a permission error on ‘/var/lib/odoo/.local’. The owner of ‘/var/lib/odoo’ is ‘users’ however the ‘odoo’ user is not apart of the ‘users’ group. I see you posted about 8 hours ago on updating your template, you may already be aware and have fixes coming. If I find time to dig into it more and get it working I’ll post again. Quote Link to comment
Eurotimmy Posted January 11 Author Share Posted January 11 Hey @menuscreen, thank you for reporting and the template has just updated in CA. Sorry for the inconvenience caused on my initial template. I had been wondering if it was something I’d done incorrectly, stopping the new version from publishing in CA. But the CA flow of updates has been reviewed and correctly passing changes to templates again now. In short, the new template has a cutdown version of the paths and (just config and add-ons now) and the config file is the way it’s working for me. Please check the new config in CA to see what I stripped out to be done instead in the config file and that got me up and running quickly. Here is the direct link to a short README I’m putting together for this. https://github.com/Eurotimmy/unraid-templates/blob/main/Odoo17/README.md Please let me know if there’s any troubles after the changes are made and the odoo.conf is in place? Quote Link to comment
ProLoader Posted January 12 Share Posted January 12 Hey @Eurotimmy, first of all thank you for your efforts for creating a working Odoo17 container for Unraid! I am still encountering a problem, there is something wrong with the permissions within the container. I suspect that the Odoo user has an incorrect UID/GID. I'm an unraid/docker noob, but in other templates the UID is set to 99 (nobody) and the GID is set to 100 in most cases (unraid-side default?). The /etc/odoo directory is assigned 99:users, but the odoo user has 101:101 and there is no users group. My configuration file is set in /etc/odoo/odoo.conf with your template as described in your readme. Since the docker crashes a few seconds after startup, I could not check the directory permissions in more detail. Log: grep: /etc/odoo/odoo.conf: Permission denied grep: /etc/odoo/odoo.conf: Permission denied grep: /etc/odoo/odoo.conf: Permission denied grep: /etc/odoo/odoo.conf: Permission denied /etc/passwd: root:x:0:0:root:/root:/bin/bash daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin bin:x:2:2:bin:/bin:/usr/sbin/nologin sys:x:3:3:sys:/dev:/usr/sbin/nologin sync:x:4:65534:sync:/bin:/bin/sync games:x:5:60:games:/usr/games:/usr/sbin/nologin man:x:6:12:man:/var/cache/man:/usr/sbin/nologin lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin mail:x:8:8:mail:/var/mail:/usr/sbin/nologin news:x:9:9:news:/var/spool/news:/usr/sbin/nologin uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin proxy:x:13:13:proxy:/bin:/usr/sbin/nologin www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin backup:x:34:34:backup:/var/backups:/usr/sbin/nologin list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin _apt:x:100:65534::/nonexistent:/usr/sbin/nologin odoo:x:101:101::/var/lib/odoo:/usr/sbin/nologin ls -la /etc: $ ls -la /etc total 324 drwxr-xr-x 1 root root 1654 Jan 12 11:44 . drwxr-xr-x 1 root root 200 Jan 12 11:44 .. -rw------- 1 root root 0 Dec 11 15:04 .pwd.lock drwxr-xr-x 1 root root 162 Dec 16 10:31 X11 -rw-r--r-- 1 root root 3028 Dec 11 15:04 adduser.conf drwxr-xr-x 1 root root 7630 Jan 4 22:06 alternatives drwxr-xr-x 1 root root 162 Dec 11 15:04 apt -rw-r--r-- 1 root root 2319 Jan 6 2022 bash.bashrc -rw-r--r-- 1 root root 367 Dec 16 2020 bindresvport.blacklist drwxr-xr-x 1 root root 16 Dec 16 10:31 ca-certificates -rw-r--r-- 1 root root 5892 Dec 16 10:31 ca-certificates.conf drwxr-xr-x 1 root root 20 Dec 11 15:08 cloud drwxr-xr-x 1 root root 22 Dec 11 15:07 cron.d drwxr-xr-x 1 root root 28 Dec 11 15:07 cron.daily -rw-r--r-- 1 root root 2969 Feb 20 2022 debconf.conf -rw-r--r-- 1 root root 13 Aug 22 2021 debian_version drwxr-xr-x 1 root root 14 Dec 11 15:07 default -rw-r--r-- 1 root root 604 Sep 16 2018 deluser.conf drwxr-xr-x 1 root root 50 Dec 11 15:07 dpkg -rw-r--r-- 1 root root 685 Jan 8 2022 e2scrub.conf -rw-r--r-- 1 root root 106 Dec 11 15:04 environment -rw-r--r-- 1 root root 1816 Dec 27 2019 ethertypes drwxr-xr-x 1 root root 52 Dec 16 10:31 fonts -rw-r--r-- 1 root root 37 Dec 11 15:04 fstab -rw-r--r-- 1 root root 2584 Feb 3 2022 gai.conf drwxr-xr-x 1 root root 18 Jan 4 22:06 ghostscript -rw-r--r-- 1 root root 458 Jan 4 22:07 group -rw-r--r-- 1 root root 446 Dec 11 15:04 group- -rw-r----- 1 root shadow 383 Jan 4 22:07 gshadow -rw-r----- 1 root shadow 374 Dec 11 15:04 gshadow- drwxr-xr-x 1 root root 12 Feb 21 2022 gss -rw-r--r-- 1 root root 92 Oct 15 2021 host.conf -rw-r--r-- 1 root root 13 Jan 12 12:01 hostname -rw-r--r-- 1 root root 175 Jan 12 12:01 hosts drwxr-xr-x 1 root root 60 Jan 4 22:07 init.d -rw-r--r-- 1 root root 1748 Jan 6 2022 inputrc -rw-r--r-- 1 root root 26 Aug 2 15:14 issue -rw-r--r-- 1 root root 19 Aug 2 15:14 issue.net drwxr-xr-x 1 root root 20 Dec 11 15:04 kernel -rw-r--r-- 1 root root 11999 Jan 4 22:07 ld.so.cache -rw-r--r-- 1 root root 34 Dec 16 2020 ld.so.conf drwxr-xr-x 1 root root 60 Dec 11 15:07 ld.so.conf.d -rw-r--r-- 1 root root 267 Oct 15 2021 legal -rw-r--r-- 1 root root 191 Mar 17 2022 libaudit.conf lrwxrwxrwx 1 root root 27 Dec 16 10:31 localtime -> /usr/share/zoneinfo/Etc/UTC drwxr-xr-x 1 root root 30 Dec 16 10:31 logcheck -rw-r--r-- 1 root root 10734 Nov 11 2021 login.defs drwxr-xr-x 1 root root 46 Jan 4 22:07 logrotate.d -rw-r--r-- 1 root root 104 Aug 2 15:13 lsb-release -rw-r--r-- 1 root root 0 Dec 11 15:08 machine-id -rw-r--r-- 1 root root 111 Sep 11 19:59 magic -rw-r--r-- 1 root root 111 Sep 11 19:59 magic.mime -rw-r--r-- 1 root root 1598 Dec 16 10:31 mailcap -rw-r--r-- 1 root root 449 Dec 11 2021 mailcap.order -rw-r--r-- 1 root root 72029 Mar 21 2022 mime.types -rw-r--r-- 1 root root 744 Jan 8 2022 mke2fs.conf lrwxrwxrwx 1 root root 12 Jan 12 11:44 mtab -> /proc/mounts -rw-r--r-- 1 root root 767 Mar 24 2022 netconfig -rw-r--r-- 1 root root 91 Oct 15 2021 networks -rw-r--r-- 1 root root 494 Dec 16 2020 nsswitch.conf drwxrwx--- 1 99 users 18 Jan 12 11:26 odoo drwxr-xr-x 1 root root 0 Dec 11 15:04 opt lrwxrwxrwx 1 root root 21 Aug 2 15:14 os-release -> ../usr/lib/os-release -rw-r--r-- 1 root root 552 Aug 12 2020 pam.conf drwxr-xr-x 1 root root 290 Dec 11 15:07 pam.d -rw-r--r-- 1 root root 970 Jan 4 22:07 passwd -rw-r--r-- 1 root root 970 Jan 4 22:07 passwd- drwxr-xr-x 1 root root 6 Dec 16 10:31 perl drwxr-xr-x 1 root root 62 Dec 16 10:32 postgresql-common -rw-r--r-- 1 root root 582 Oct 15 2021 profile drwxr-xr-x 1 root root 32 Dec 11 15:07 profile.d -rw-r--r-- 1 root root 2932 Apr 1 2013 protocols drwxr-xr-x 1 root root 26 Dec 16 10:31 python3 drwxr-xr-x 1 root root 32 Dec 16 10:31 python3.10 drwxr-xr-x 1 root root 14 Jan 4 22:07 rc0.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc1.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc2.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc3.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc4.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc5.d drwxr-xr-x 1 root root 14 Jan 4 22:07 rc6.d drwxr-xr-x 1 root root 44 Dec 16 10:31 rcS.d -rw-r--r-- 1 root root 85 Jan 12 12:01 resolv.conf lrwxrwxrwx 1 root root 13 Dec 5 06:15 rmt -> /usr/sbin/rmt -rw-r--r-- 1 root root 887 Apr 1 2013 rpc drwxr-xr-x 1 root root 266 Dec 11 15:07 security drwxr-xr-x 1 root root 26 Dec 11 15:06 selinux -rw-r--r-- 1 root root 12813 Mar 27 2021 services drwxr-xr-x 1 root root 76 Jan 4 22:07 sgml -rw-r----- 1 root shadow 527 Jan 4 22:07 shadow -rw-r----- 1 root shadow 527 Jan 4 22:07 shadow- -rw-r--r-- 1 root root 128 Dec 11 15:05 shells drwxr-xr-x 1 root root 54 Dec 11 15:04 skel drwxr-xr-x 1 root root 46 Dec 16 10:31 ssl -rw-r--r-- 1 root root 0 Dec 11 15:04 subgid -rw-r--r-- 1 root root 0 Dec 11 15:04 subuid -rw-r--r-- 1 root root 2355 Feb 25 2022 sysctl.conf drwxr-xr-x 1 root root 308 Dec 11 15:07 sysctl.d drwxr-xr-x 1 root root 20 Feb 15 2022 systemd drwxr-xr-x 1 root root 12 Dec 11 15:07 terminfo -rw-r--r-- 1 root root 8 Dec 16 10:31 timezone -rw-r--r-- 1 root root 1260 Jun 16 2020 ucf.conf drwxr-xr-x 1 root root 92 Dec 11 15:07 update-motd.d -rw-r--r-- 1 root root 681 Mar 23 2022 xattr.conf drwxr-xr-x 1 root root 176 Jan 4 22:07 xml Quote Link to comment
Eurotimmy Posted January 12 Author Share Posted January 12 Hey @ProLoader, glad you’re giving the container a spin on Unraid and I hope I can assist you. Please go in to the CLI / shell on your Unraid system (not in the Odoo container) and check the ‘odoo.conf’ file is in the path you set as “Config Location” when you installed the Odoo17 container. To do this you’ll need to use the “Terminal” option in the top right-hand corner of your Unraid web interface. FWIW my ‘odoo.conf’ is owned by root:root and additionally if I access the Odoo17 container via “Console” in the Docker screen the location “/etc/odoo” is also owned by 99:users (which should be fine, I believe). Please let us know if your Unraid host folder (for eg /mnt/user/appdata/odoo/config) is showing the Odoo.conf file and that it has all your personal config correctly in it? If you edit the file to correct any configuration please remember to restart the Odoo17 container. Quote Link to comment
ProLoader Posted January 12 Share Posted January 12 (edited) Thanks for your fast Reply. I hope that the information below is the info you need. I have tested the connection configuration to the postgresql DB externally and it works so far. Template: CLI: root@Unraid:~# cd /mnt/user/appdata/odoo/ root@Unraid:/mnt/user/appdata/odoo# ls config/ data/ extra-addons/ root@Unraid:/mnt/user/appdata/odoo# cd config/ root@Unraid:/mnt/user/appdata/odoo/config# ls odoo.conf root@Unraid:/mnt/user/appdata/odoo/config# ls -la -rw-rw-rw- 1 root root 954 Jan 12 11:30 odoo.conf odoo.conf: [options] addons_path = /mnt/extra-addons data_dir = /var/lib/odoo admin_passwd = censoredmypw db_host = 192.168.2.254 db_port = 5433 db_user = odoo db_password = censoredmypw db_name = odoo ; csv_internal_sep = , ; db_maxconn = 64 ; db_name = False ; db_template = template1 ; dbfilter = .* ; debug_mode = False ; email_from = False ; limit_memory_hard = 2684354560 ; limit_memory_soft = 2147483648 ; limit_request = 8192 ; limit_time_cpu = 60 ; limit_time_real = 120 ; list_db = True ; log_db = False ; log_handler = [':INFO'] ; log_level = info ; logfile = None ; longpolling_port = 8072 ; max_cron_threads = 2 ; osv_memory_age_limit = 1.0 ; osv_memory_count_limit = False ; smtp_password = False ; smtp_port = 25 ; smtp_server = localhost ; smtp_ssl = False ; smtp_user = False ; workers = 0 ; xmlrpc = True ; xmlrpc_interface = ; xmlrpc_port = 8069 Thanks in advance! Edited January 12 by ProLoader Quote Link to comment
Eurotimmy Posted January 12 Author Share Posted January 12 Hey @ProLoader… looking good but I’m going to take a shot at that ‘data’ drive mapping. Would you mind please removing that path mapping from your Odoo17 container (via the ‘Edit’ option) and restarting the Odoo17 container. I had tried mapping /var/lib/odoo to /mnt/user/appdata/odoo/data when I did it, but I recall that when I had that mapped it halted my Odoo from starting too. Quote Link to comment
ProLoader Posted January 12 Share Posted January 12 Hey @Eurotimmy, I finally managed to get it working. After playing around a bit, I tried to make the odoo user inside the docker the owner of the mounted paths. chown -R odoo:101 /etc/odoo chown -R odoo:101 /mnt/extra-addons This fixed it for me. If I can help you in any way with any tests, I'd be happy to help. Thanks for your help! Quote Link to comment
Eurotimmy Posted January 12 Author Share Posted January 12 Hi @ProLoader That’s an interesting one, glad you shared the fix as it’ll likely help others in future. Enjoy your new Odoo. Quote Link to comment
MarianKoniuszko Posted January 16 Share Posted January 16 Hello @Eurotimmy it's possible to make that app without examples. It's very frustrating to seek how to delete all of them or change names, admin etc. Regards. Quote Link to comment
S3v3nD34dly51ns Posted January 19 Share Posted January 19 (edited) so after some trial and error I was successfully able to get Odoo up and running. I have stumbled through this multiple times only due to the fact of my own errors. For those having issues I will attempt to break down the easiest way of installing and getting it running. However the only issue I am having is editing my site after processing it though NGINX, as it just sits there and rotates when accessing it through https: . 1. Installed a PostGRES15 instance named "odoo-DB" points to port 5499 2. Installed Odoo17, named the database, PW and user fields within the config file itself. 3. Following the directions that Eurotimmy put within the readme file which you can find here https://github.com/Eurotimmy/unraid-templates/blob/main/Odoo17/README.md (adjust IP address, ports and DB fields as necessary to meet your requirements) [options] addons_path = /mnt/extra-addons data_dir = /var/lib/odoo admin_passwd = admin db_host = 192.168.55.9 db_port = 5499 db_user = odoo db_password = odoo db_name = odoo ; csv_internal_sep = , ; db_maxconn = 64 ; db_name = False ; db_template = template1 ; dbfilter = .* ; debug_mode = False ; email_from = False ; limit_memory_hard = 2684354560 ; limit_memory_soft = 2147483648 ; limit_request = 8192 ; limit_time_cpu = 60 ; limit_time_real = 120 ; list_db = True ; log_db = False ; log_handler = [':INFO'] ; log_level = info ; logfile = None ; longpolling_port = 8072 ; max_cron_threads = 2 ; osv_memory_age_limit = 1.0 ; osv_memory_count_limit = False ; smtp_password = False ; smtp_port = False ; smtp_server = False ; smtp_ssl = True ; smtp_user = False ; workers = 0 ; xmlrpc = True ; xmlrpc_interface = ; xmlrpc_port = 8069 ; xmlrpcs = True ; xmlrpcs_interface = ; xmlrpcs_port = 8071 Copied the config file and adjusted accordingly (see above), once Odoo was installed. Went to Unraid>Tools>New Permissions and selected 'Shares' and chose 'appdata'. (Keep in mind to do this a little easier make sure that SMB is temporarily enabled for your appdata share folder). Let the new permissions run it's course (takes about 7-10 minutes, longer in some cases). Once it's finished using your text edited config file (I used Notepad++) save file as odoo.conf in appdata\odoo\config. *Note: This is just easier for me, however you can do all of this using the Unraid Terminal as Eurotimmy described above. 4. Start the Odoo17 container, click on the container and watch the Logs, everything should start populating. Once loaded go to the WebUI (http://your.internal.ip.address:port). Should see it has loaded up. 5. Log in with default credentials admin, admin. 6. Seeing as I Already have NGINX installed that points to http://internal.ip.address:8069, and also created an instance on my hosting service that points to https://my.domainname.com and NGINX creates it's SSL cert. 7. After first initial boot, do not forget to delete the -i base within the container Advanced Tab>Post Arguments and then restart your Odoo container. I have this also stop my database when I did this, so make sure to restart your DB if this happens. If everything is operating as it should, you should be able to access Odoo WebUI with no issues. Now the only problem I am having like I said earlier is everything works on the https: side of things with the only exception of the web editor. As soon as I click on 'Edit' on my site, it goes to a grey screen and just a spinning wheel. Now I've done a little digging and found several instances of this happening on earlier versions of Odoo and it's actually due to the configuration end on NGINX. Many report adding add_header 'Content-Security-Policy''upgrade-insecure-requests'; to the config file for NGINX for this instance will work around that. However that is not the case for me. I am wondering if anyone else is having a similar issue and whether or not you have found a fix? As I am setting up a site for a person who would like to edit this site for their own and they are not on prem and cannot edit from within the local network. Edited January 19 by S3v3nD34dly51ns Quote Link to comment
Eurotimmy Posted January 24 Author Share Posted January 24 (edited) On 1/20/2024 at 1:24 AM, S3v3nD34dly51ns said: As soon as I click on 'Edit' on my site, it goes to a grey screen and just a spinning wheel. Now I've done a little digging and found several instances of this happening on earlier versions of Odoo and it's actually due to the configuration end on NGINX. Many report adding add_header 'Content-Security-Policy''upgrade-insecure-requests'; to the config file for NGINX for this instance will work around that. However that is not the case for me. I am wondering if anyone else is having a similar issue and whether or not you have found a fix? As I am setting up a site for a person who would like to edit this site for their own and they are not on prem and cannot edit from within the local network. Hi @S3v3nD34dly51ns, thanks for trying my Odoo17 template and giving feedback. Appologies on my delay as I needed to recreate / do some research of your issue... which I have recreated and (I think) fixed. Note: I updated the README and my example odoo.conf file linked in the first post above The steps to correct this should be... Step 1. Edit the odoo.conf file to include this setting: proxy_mode = True Step 2. In your NGINX (or in my case NGINX Proxy Manager) settings, edit your location/{ ... } to include the following: proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_redirect off; proxy_pass $forward_scheme://$server:$port; Please give it a try and let me know if this helped at all? Edited: Additional material from Odoo about HTTPS / Proxy setup Edited January 24 by Eurotimmy Added a link to Odoo docs Quote Link to comment
jrmcmillan Posted February 27 Share Posted February 27 I too am having trouble getting Odoo to start. I've followed the template instructions but I'm getting logfile error messages - which I'm guessing are permissions issues. Here's the Odoo docker config: Here's the Postgresql15 docker config: Here's the Odoo config file: And here's the log files from Odoo and Postgresql15, respectively. It doesn't seem to recognize the user "odoouser". However, it is set up as an Unraid user as well as in the docker/config files. Any help would be appreciated. Quote Link to comment
Eurotimmy Posted February 29 Author Share Posted February 29 Hey @jrmcmillan, thanks for giving Odoo17 a try. I'll try to assist you as best I can. Please check: On a fresh Postgres database, you ran the Odoo17 container for the very first time with the "Post Arguments" field set to -i base ... THEN, you removed the "-i base" from the "Post Arguments" field and restarted both Postgres and Odoo17 Also, I found a couple of threads (addmittedly I feel they could be long shots) about adding the "PGUSER" environment variable to the Docker environment. In Unraid it would look like the attached example for anybody else reading this. Please consider (if safe to do so) redoing the database part again...? In Unraid Docker tab Remove the 'postgresql15' docker your using for Odoo (Remove, Yes) Delete "/mnt/cache/appdata/postgresql15" (if you're comfortable to remove that folder) In the Odoo17 container, add "-i base --without-demo=all --stop-after-init" in to "Post Arguments" Add a new 'postgesql15' Docker container, configure it and start it Run Odoo17 container one time It should run and stop on it's own View it's 'Logs' to see if it initialised the database Let us know how you go? Cheers! Quote Link to comment
jrmcmillan Posted February 29 Share Posted February 29 Hi Eurotimmy. It's now working! I think the key was deleting the database completely and removing the appdata file, then reinstalling. It obviously didn't like something from the initial setup, but it's now working fine. (I didn't do anything with the PGUSER stuff). Thanks for the help. Quote Link to comment
jrmcmillan Posted March 1 Share Posted March 1 One more question: I assume what I have is Odoo running on my Unraid server with the database also on my Unraid server. I'm thinking it has nothing to do with Odoo running on an Odoo server and database. The initial configuration comes with the Invoicing module. I'd like to add the accounting module. However, when I do, I get sent to an Odoo server and end up creating a database on their server - which I don't want to do. So, my question is: how do I install Odoo apps on my Unraid server, using my local database? Quote Link to comment
Poundsy Posted March 14 Share Posted March 14 (edited) On 3/1/2024 at 12:29 PM, jrmcmillan said: The initial configuration comes with the Invoicing module. I'd like to add the accounting module. However, when I do, I get sent to an Odoo server and end up creating a database on their server - which I don't want to do. So, my question is: how do I install Odoo apps on my Unraid server, using my local database? It appears this is the community version of Odoo. To get the accounting module you need to upgrade to enterprise version, you'll notice when you look at the accounting module there is no activate button but rather an upgrade button. There is an upgrade that needs to be done as per here. I'm going to have a tinker and see what I can work out. Edit: I believe I have enterprise working. Be aware that doing this will start a 30 day trial, after that time you will be required to purchase a year long subscription. Back your shit up!!!!!!!!!!!!!!!! You need to get the web_enterprise module and throw it in the extra-addons folder. It was mapped when installing the Odoo docker container. It will be something like /mnt/user/appdata/odoo/extra-addons/ I found the web_enterprise addon in the source install. I downloaded those files here. Grab the enterprise source. Open that archive and dive into this folder \odoo-17.0+e.20240313\odoo\addons and find a folder called web_enterprise. Copy that folder to your extra-addons folder. Now go and edit the Odoo container, switch on advanced view and pop the following in your Post Arguments: -d <database_name> -i web_enterprise --stop-after-init Replace <database_name> with the name of your database you configured in odoo.conf, don't include < or > in the database name. Apply and run the Odoo container. It will run, upgrade the database then stop. You can check logs to see if there was any funny business. Edit the Odoo container again, remove the text we put in Post Arguments and hit apply. The container should now start up in enterprise mode and you'll have a nifty little dashboard with all the apps you use regularly. Edit 2: Found an issue. While it allows you to activate your sub, it seems to not want to play ball with the app installer. After play around some more it decided to go back to telling me I need to upgrade. Working on another ideal. Edit 3: After some tinkering, I found if you copy all the sub folders in the addons folder from the source install archive into your extra-addons folder, remove the odoo container completely, then run -d <database_name> -i web_enterprise --stop-after-init on install, edit container then remove those args and start everything up normally those upgrade buttons become activate buttons. Now the only problem I seem to have is on the app selection screen are my icons are missing their action icon pictures are just show a box with a ! in it. Anything I install after the upgrade however seems to have an icon. Edit 4: Everything was going well until I tried to activate the knowledge module. Now it's just throwing a bunch of errors about missing modules and unmet dependencies. As much as I like docker, I think I'm going to end up spinning up a linux VM to make this work. Edited March 15 by Poundsy Quote Link to comment
jrmcmillan Posted March 16 Share Posted March 16 Thanks for all your work. At this point, I think I'll just stay with the community version and the free functionality. However, I've got another issue/question. My config is happy running Unraid (and Odoo) in unsecured mode (http:). I installed Tailscale and added it to my Unraid server, local pc, and remote laptop (I'm a consultant and on the road quite a bit). This gives me remote access to both the Unraid server and Odoo, and works fine for my situation (single user and defined Tailscale network). I'd like to enable the email functionality in Oodo, but it only wants to connect to the Odoo database via a secured connection (https:). My assumption is Odoo cannot have a secured connection unless Unraid uses a secured connection. I'm stuck because I don't know how to setup Unraid with a secured connection. I've tried to follow the Unraid docs, but I haven't had any success using a self-generated certificate and don't know how to go any further. So, 2 questions: 1) Is my assumption correct regarding needing to get Unraid working with a secured access first? If so, how do I do that? 2) Using Odoo's email plugin (Outlook), it asked for the database's address. I assume it's [https://local IP address:8069]. Is that right? Or is it something else? I have virtually no Linux command line experience and have only gotten Odoo and Plex dockers working because of the good templates and YouTube. Any help would be appreciated. Quote Link to comment
Poundsy Posted March 21 Share Posted March 21 I don't know anything about self generated certs. I use cloudflare to manage that stuff, so no idea how to help with problem 1. Problem 2 is easy. As long as your postgres is installed on defaults then your port is 5432. Depending on how everything is setup it could just be a case of one of the following; localhost:5432 - only works if both database and odoo are on the same machine. 127.0.0.1:5432 - this is generally bad practice however since 127.0.0.1 is a loopback address. Your servers local IP such as 192.168.x.x:5432 or 10.x.x.x:5432 I recommend setting your server to a static IP in your router so it never changes. Change your DHCP pool to exclude a few addresses at the bottom of your range then use those addresses as static IPs. Quote Link to comment
NexusEFR Posted Wednesday at 03:54 PM Share Posted Wednesday at 03:54 PM On 1/24/2024 at 4:52 AM, Eurotimmy said: Hi @S3v3nD34dly51ns, thanks for trying my Odoo17 template and giving feedback. Appologies on my delay as I needed to recreate / do some research of your issue... which I have recreated and (I think) fixed. Note: I updated the README and my example odoo.conf file linked in the first post above The steps to correct this should be... Step 1. Edit the odoo.conf file to include this setting: proxy_mode = True Step 2. In your NGINX (or in my case NGINX Proxy Manager) settings, edit your location/{ ... } to include the following: proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_redirect off; proxy_pass $forward_scheme://$server:$port; Please give it a try and let me know if this helped at all? Edited: Additional material from Odoo about HTTPS / Proxy setup Hello Eurotimmy, great contribution with your manual for Odoo. I am having problems with stability and data persistence that are being uploaded to Odoo, such as profile images or icons of applications that are being installed. I don't know if anyone else is experiencing this issue or if there is a parameter that solves this: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/odoo/filestore/Odoo/a9/a9f6... Additionally, I believe I should configure the NPM as you mentioned. I already have the Proxy mode = true activated, but I don't know which parameters are unique to my configuration in all these lines that need to be added : proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_redirect off; proxy_pass $forward_scheme://$server:$port; I understand that each line should have unique values from my server, but I don't understand which part should be kept and which should be replaced. Could you give me some hints, please? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.