I deployed Odoo 13 on AWS. But it shows this error when connecting:
GET https://****-erp.sit.solpass.co/web/content/497-9d3f564/web.assets_common.css net::ERR_ABORTED 404
web?debug=0:38 GET https://****-erp.sit.solpass.co/web/content/503-4926ae1/web.assets_backend.css net::ERR_ABORTED 404
web?debug=0:39 GET https://****-erp.sit.solpass.co/web/content/504-9d3f564/web.assets_common.js net::ERR_ABORTED 404
web?debug=0:40 GET https://****-erp.sit.solpass.co/web/content/505-4926ae1/web.assets_backend.js net::ERR_ABORTED 404
web?debug=0:52 Uncaught TypeError: odoo.define is not a function
at web?debug=0:52
I think my issue appear because my Odoo can not access these Js, Css file.
And when I access it by normal debug or debug with assets, it's run normally
Most critical level of issue, SnippetBucket Team is expert on ODOO to resolve all critical issues.
DELETE FROM ir_attachment WHERE name SIMILAR TO '%.(js|css)';
For ODOO 13,14 version I confirmed.
We SnippetBucket.com face critical same issues for plenty of clients. But with this SQL delete old reference, than after restart ODOO and access backend and front-end, it 1000% worked for us.
sudo service odoo restart
or
sudo service odoo-server restart
Restart based on your linux/window or mac
Make sure when you restore your database successful restore all filestore. I better suggest on backup and restore, filestore manually copy and restore based on "data" location
After deleting all attachments on the database and restart Odoo on server. It was resolved
Related
I am trying to run Odyssey locally, but getting a "security sever may be unreachable or offline" error in the navigator. I've tried testing the EAF security service to make sure it is running and ran into a 404 page error.
I used
"http://[YOURSERVERNAMEHERE]/EAF/Odyssey/[Your Site ID]/Security/Service?Partition=[Your Site ID]&Username=system&Password=tsg"
replacing some of the info with my configuration.
Ubuntu 20.04
Apache 2.4.41
phpmyadmin 4.9.5deb2
I can log in to phpmyadmin and see the main page where the databases are listed in the left-hand panel. But I get an error message. Using F12, I see the following error:
Failed to load resource: the server responded with a status of 403 (Forbidden) config.js:1
There is a config.js file under /usr/share/phpmyadmin/js. There are other js files in that folder that are included in the sources listed in the browser (again, using F12).
I confirmed that the config.js file has read permissions set for everyone. All the js files in that folder have the same permissions set.
I also confirmed that /etc/apache2/conf_enabled/phpmyadmin.conf links to /etc/apache2/conf_available/phpmyadmin.conf and that links to /etc/phpmyadmin/apache.conf. Neither this apache.conf nor /etc/apache2/apache2.conf deny access to config.js.
When I delete config.js, I do not get the error BUT I get other errors concerning functions that are contained in that config.js (like "Uncaught ReferenceError: isStorageSupported is not defined."). This tells me that the forbidden file is indeed this file. I renamed it and created a new empty config.js - still get the same forbidden error(fwiw).
We've been using phpmyadmin on this server since April. The error has cropped up in the last couple weeks. When I ssh'd into the server this week, it displayed a message that it needed restarted to make updates. I did not know there were auto-updates going on. I restarted, which did not help the problem. Then I updated and upgraded everything but still no help. I uninstalled (remove and purge) and installed phpmyadmin, but still no help.
My next step would be to upgrade phpmyadmin to the latest stable using a different repository (the debian repo is a little behind). But I thought I'd ask here because I have a feeling that might not help either.
I'm thinking that something changed in the server stack that isn't allowing the config.js file to be read; I just have no idea what that would be. Has anyone else seen this or something similar?
I implemented a band-aid: I copied the /usr/share/phpmyadmin/js/config.js file to config.1.js. I edited the code in /usr/share/phpmyadmin/libraries/classes/Header.php to use config.1.js instead of config.js.
No error now!
But I don't like this answer because it doesn't tell me what the original source of the problem is and how to keep it from happening again.
To start I'm not a coding expert so excuse me if this was a newbie question.
I have installed a nodejs app into my VPS (digital ocean), after uploading everything (both server side and client side) seem to be running but I'm having an issue.
The dependencies are managed using bower so installed everything in the root directory of Apache server. As I use the "Inspect Element" in my browser to see
the console I get a first error of:
http://104.131.66.68/manager/bower_components/socket.io-client/dist/socket.io.min.js Failed to load resource:
the server responded with a status of 404 (Not Found)
I checked the bower_components folder in my server and the folder socket.io-client exists! But when I checked through my browser to see the source files it is not there! Other dependencies are available.
These are the errors that appear, the socket.io error at the top most i suspect the reset are due to the same problem and lastly is the API Key (i intend to handle that after this).
your help is highly appreciated!!
Thank you
<script src="/socket.io/socket.io.js"></script> use this to serve the socket.io client. If it does not work, you are having something wrong somewhere.
When I'm trying to open any app in IIS Manager (local machine) like CGI, Handler mappings etc. I got an error There was an error while performing this operation:
I'm unable to find out this issue.
I installed the hosting bundle again. i.e. repair and then checked if the iis_usr has all access for the wwwroot folder.
This resolved the problem for me.
I can't seem to get an asp site to run with ISPCONFIG3 at all. I am getting errors in the apache error.log like this:
Not running mod-mono-server.exe because no MonoApplications, MonoApplicationsConfigFile or MonoApplicationConfigDir specified.
Failed to connect to mod-mono-server after several attempts to spawn the process.
I think it has to do with my configuration somehow but I can't seem to figure out where. Thoughts?
Encountered this error today after installing apache2, mod-mono, etc in Ubuntu 19.04 on my laptop. Having just done it successfully on an AWS instance running Ubuntu 18.04, I was surprised that it didn't work here. By trial and error tweaking the mono-server config, apache2 config, the ASP.NET web app folder (with a simple index.aspx in it), and looking at the apache2 error logs after each change (after stopping/restarting apache2 each time!), I discovered that, in my case at least, this error was caused by the absence of a web.config file in the web app root folder; as soon as I created a simple skeleton web.config file, this error message went away.
Worth noting in passing is that the error message contains a typo: there should be an "s" for "Applications" in the keyword MonoApplicationConfigDir, like the other two keywords have. One of the things I tried was to alter the MonoApplicationsConfigDir statement that was present by default in my mono-server4-hosts.conf file by removing the "s" to match the error message, but that generated a different, fatal error that prevented apache2 from starting: systemctl status apache2.service showed "Invalid command 'MonoApplicationConfigDir'".