-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Files not found: Error 502 Bad gateway #3628
Comments
This time it has nothing to do with the aforementioned. Sometimes the socket is disconnected and the board can no longer be seen in other occasions mongodb stops responding To solve all the cases that he mentions, wekan had to be reinstalled, and I can't continue for another year reinstalling every time something stops working correctly. Nor is it a solution that changes or moves to ubuntu server since the server where it lives is from a client and they have centos. I have not been able to follow up on the previous cases due to time zone. Now I understand a little more about how wekan works with snap and this time I will give it a timely follow-up |
Ok, so probably related to In Progress speedups #3345
Many use Wekan on CentOS. |
Good day I reviewed in detail what they comment but it did not help me to solve my problem. I have loaded my previous backups and even so the document has been lost, in the path that wekan is looking for, it cannot download it and it is with some files I connect correctly to the mongo database locally on the centos server but I don't know what to do I have renewed wekan following this guide but I have not been successful Apparently the error is that the socket lost the path of the document link Attached document screen when I try to download it |
Did you configure websockets? |
If Nginx does not work, try Caddy |
You seem to use CloudFlare. Caddy CloudFlare config is here: |
Backup restore info is here: |
When you used Nginx, did you allow bigger attachment size like info here? |
You did show above empty database that is at port 27017 when you installed MongoDB 4.2.x. That empty raw database files could be at /var/lib/mongodb/ But real Wekan database is included in Wekan Snap at port 27019, with raw database files at /var/snap/wekan/common , you can connect to it this way:
Or by connecting to it with nosqlbooster GUI But I don't know why you should access database directly. With Wekan you can at All Boards page move mouse to top of board icon and click star to make it your bookmark link at top. |
Are you trying to use API ? Or what are you trying to do? |
I was trying to connect on my server locally to mongo to explore the database and know if it was connected correctly. I still can't see my documents that were uploaded to the board |
Attachments can be seen with nosqlbooster |
Good day Random files cannot be viewed within wekan, the file exists in the database but the web application cannot find it, it seems that the path of the document changed or was modified |
Is the same errors also with only Wekan http, without Nginx/Caddy in front of Wekan? I'm just thinking, could it be some misconfiguration in Nginx. Are there any other errors in browser inspect console? Can you copy all that content to comment of this issue, anonymized by removing your server domain and IP addresses? |
Do you have in same Nginx config also other settings for some other website, like some PHP website like Drupal? Those settings could prevent Wekan from accessing files. That |
Are there any special charaters in attachment filenames, like chinese, russian, scandinavian öÖäÄåÅ, or other non-Latin characters? Because currently Wekan has bug that uploading those files works, but downloading crashes Wekan. |
For fixing that filename bug, there is #3273 but I have not tested it well enough yet, it's not yet merged to Wekan. Previously there was fix to this issue, but that fix stopped working after I upgraded to newer version of Meteor www.meteor.com full stack Javascript web framework. Wekan is coded with Meteor. |
I don't know is it possible that you would send your MongoDB database Backup as .zip or .7z archive to me by you creating free Protonmail account https://protonmail.com (Protonmail automatically end-to-end encrypts email between protonmail email addresses) to my paid Protonmail address [email protected] so that I would try to find that bug and fix it. Those that have previously sent their database to me have made it easy for me to find that bug and release fix fast, because problem in general is reproducing bug locally, so I can make code changes and see does code change fix that bug. After fixing bug I delete received database. |
For non-Protonmail email addresses, it's possible to use PGP to send encrypted email to me. |
Sure, I will send you an email with the request |
I send you my database from the email [email protected] |
Issue
Email settings:
Add these issues to elsewhere:
Other Wekan issues can be added here.
Server Setup Information:
Note: Please anonymize info, and do not add to this public issue any of your Wekan board URLs, passwords, API tokens etc, do you understand?:
Did you test in newest Wekan?: No
For new Wekan install, did you configure root-url correctly so Wekan cards open correctly https://github.com/wekan/wekan/wiki/Settings ?
Wekan version:
snap.wekan.wekan.service - Service for snap application wekan.wekan
Loaded: loaded (/etc/systemd/system/snap.wekan.wekan.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2021-03-03 14:19:02 CST; 1min 23s ago
Main PID: 6739 (wekan-control)
CGroup: /system.slice/snap.wekan.wekan.service
├─6739 /bin/bash /snap/wekan/1394/bin/wekan-control
└─7555 /snap/wekan/1394/bin/node main.js
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: SAML_PRIVATE_KEYFILE= (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: SAML_PUBLIC_CERTFILE= (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: SAML_IDENTIFIER_FORMAT= (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: SAML_LOCAL_PROFILE_MATCH_ATTRIBUTE= (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: SAML_ATTRIBUTES= (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: ORACLE_OIM_ENABLED=false (default value)
Mar 03 14:19:04 prdbambu01.cloud wekan.wekan[6739]: MONGO_URL=mongodb://127.0.0.1:27019/wekan
Mar 03 14:19:08 prdbambu01.cloud wekan.wekan[6739]: Presence started serverId=uJmuzibNkFfXznMHk
Mar 03 14:19:11 prdbambu01.cloud wekan.wekan[6739]: {"line":"87","file":"percolate_synced-cron.js","message":"SyncedCron: Scheduled "notification_cleanup" next run @Wed Mar 03 2021 14:19:11 GMT-0600 (Central Standard Time)","time":{"$date":161480...67},"level":"info"}
Mar 03 14:19:28 prdbambu01.cloud wekan.wekan[6739]: (node:7555) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Hint: Some lines were ellipsized, use -l to show in full.
If this is about old version of Wekan, what upgrade problem you have?:
Operating System: Centos 7
Deployment Method(snap/docker/sandstorm/mongodb bundle/source): Snap
Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first): Nginx
MongoDB Version: MongoDB shell version v4.2.12
Wekan only works on newest desktop Firefox/Chromium/Chrome/Edge/Chromium Edge and mobile Chrome. What webbrowser version are you using? : Chrome , firefox
Problem description:
I upload files in pdf or xml to my created tasks but after a few days when I want to download the file it shows me a 502 on the server, this happens with only some files that we upload
The text was updated successfully, but these errors were encountered: