Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
Been having an issue and finally narrowed it down, but can't find a solution.
If I setup nginx to redirect to HTTPS, everything works great, SSL connection and all, except when writing messages in Odoo, our staff can't attach files. It gets stuck on "uploading" (blue bar over the file icon). There's no useful output in the log, even on the most verbose debug level.
As a workaround, I've disabled SSL, but I'd like to turn it back on. Suggestions? Running v9.0c.
I find this same problem and using Chrome developer tool, I find that X-Frame-Options is set like DENY.
To fix it, I edit the file /etc/nginx/snippets/ssl.conf
In this file, comment this line:
add_header X-Frame-Options DENY;
and add this line:
add_header X-Frame-Options SAMEORIGIN;
sudo service nginx restartReload the Odoo page (F5) and try attach again. Must be work.
You're a HERO! This worked. Thank you so much. Really appreciate it.
Yes, it works!!!
There is no `ssl.conf` file for me!
We had similar issue in our setup running nginx as reverse proxy. The solution is simple. Just increase the upload file size limit for nginx by adding the line below to nginx.conf file
http {
client_max_body_size 50M;
//other lines...
}
Hey Onnet, I checked and ours is currently set to 300M. Shouldn't be an issue.
This worked perfectly for us. Thanks Onnet
It didn't work for me, i tried with 50M and it didn't work.
Create an account today to enjoy exclusive features and engage with our awesome community!
Реєстрація| Related Posts | Відповіді | Переглядів | Дія | |
|---|---|---|---|---|
|
0
січ. 24
|
1732 | ||
|
3
жовт. 18
|
10332 | ||
|
5
серп. 15
|
6365 | ||
|
1
вер. 20
|
5643 | ||
|
0
вер. 23
|
2196 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
Hey Onnet, I checked and ours is currently set to 300M. Shouldn't be an issue.
Just a hint to everyone reading this thread: such observation can have different causes, so you have to check your browser's console message first. Depending on the cause, you can find a solution, such as some listed here. There maybe others.