Picture cannot be show

[tangjiahao2001]

Hi, Thanks for the software, but I found an error when I used it.

Use the latest version, use docker-compose.yml .Image uploaded successfully, but cannot display

[xet7]

In docker-compose.yml, maybe you did not set ROOT_URL ? like:

• ROOT_URL=http://192.168.0.100 (your computer IP address)
• ROOT_URL=http://localhost (if only your computer locally)
• ROOT_URL=https://wekan.example.com (if you use SSL/TLS at from like Caddy/Nginx/Apache, see wiki)

[xet7]

Hmm, I think there are some bugs somewhere:

1. Attachments are only visible after reload of webpage, or move attachment to filesystem (visible) or then back to MongoDB (also then visible). Related Docker Missing Features and Odd Presentation #4797 The uploaded file cannot be displayed #4802
2. When migrating and moving attachments, createdAt/modifiedAt/updatedAt are lost Attachments updatedAt, createdAt and modifiedAt ? #4798

[tangjiahao2001]

yes, thanks for your reply, @xet7

The official demo can't display pictures either, look:

hmm, I also had a bug switching languages,

I couldn't switch languages with the latest version of wekan.

[xet7]

@tangjiahao2001

Demo board was upgraded too early, some links to images are not correct yet, it needs some fixes.

In newest Docker WeKan setting language and changing language works very well, when ROOT_URL is correct. You still have wrong setting because you have untranslated strings visible like all-boards, sort-cards. I just have problems how to explain it properly, I don't know could someone else explain it better.

ROOT_URL

Working translations in newest WeKan

Browser settings need to have only one language

For example, show WeKan in Japanese, there needs to be only Japanese selected at Firefox Preferences / Choose your preferred language for displaying pages. Delete all other languages from there, there needs to be only Japanese, like this:

After that, WeKan is in Japanese:

[tangjiahao2001]

Thank you very much for your answer. @xet7 Your answer was excellent. Now all my questions are solved

language and pictures

best regards! thanks

[mohammadZahedian]

@tangjiahao2001

Demo board was upgraded too early, some links to images are not correct yet, it needs some fixes.

In newest Docker WeKan setting language and changing language works very well, when ROOT_URL is correct. You still have wrong setting because you have untranslated strings visible like all-boards, sort-cards. I just have problems how to explain it properly, I don't know could someone else explain it better.

ROOT_URL

Working translations in newest WeKan

Browser settings need to have only one language

For example, show WeKan in Japanese, there needs to be only Japanese selected at Firefox Preferences / Choose your preferred language for displaying pages. Delete all other languages from there, there needs to be only Japanese, like this:

After that, WeKan is in Japanese:

i am using snap, and have same language problem
didn't understand what should i do now

[tangjiahao2001]

@mohammadZahedian

Maybe you could take a look at this

https://github.com/wekan/wekan/wiki/Settings

[xet7]

Yes, that is setting for WeKan server computer IP address, at local network.

[xet7]

@mohammadZahedian

According to your screenshots at #4303 (comment) you have not setup root-url correctly, because you still have menu names like -title etc. Having wrong settings also can cause attachments not visible.

If you use WeKan at local network, you can check your WeKan server IP address at network settings, or with command:

ip address

For example, if you have IP address 192.168.0.100, then use settings:

sudo snap set wekan root-url='http://192.168.0.100'
sudo snap set wekan port='80'

But change your IP address to above.

If your WeKan server is at public Internet, and you have nameserver subdomain like wekan.example.com pointing to your server like A 100.100.100.100 where you change that to your server public IP address, then you can setup Caddy 2 to provide SSL/TLS https://github.com/wekan/wekan/wiki/Caddy-Webserver-Config

So then settings would be:

sudo snap set wekan root-url='https://wekan.example.com'
sudo snap set wekan port='3001'

In this above case, Caddy would redirect from HTTP 80 to HTTPS 443, and then proxy to localhost 3001 WeKan Node.js server.

[mohammadZahedian]

i have just restored database every thing is ok except pictures and attachments...
root url is ok too...
what shoud i do now?

[mohammadZahedian]

[mohammadZahedian]

also cant import with json most of the time, espacialy when the board has attachment
@xet7

[xet7]

@mohammadZahedian

It depends can you send your mongodump backup in .zip file from free https://proton.me email account to support@wekan.team (Protonmail encrypts internal email), so that I could look what bug there is.

[bonnebulle]

Hello
Am using last version (w/ Docker)
I have the same issue ( when no port specified )
Docker env:
ROOT_URL=http://192.168.125.14

console error message :

GET
http://192.168.125.14/cdn/storage/avatars/6QB3ZGv2njJWevp5r/original/6QB3ZGv2njJWevp5r.png?auth=false&brokenIsFine=true 
[HTTP/1.1 403 Forbidden 1ms]

If I specify port it's OK
ROOT_URL=http://192.168.125.14:3080
( maybe can help others )

[mohammadZahedian]

still have translate problem

but after refresh it is fine

[xet7]

Related #4780 (comment)

[Dexus]

Hello, we have also the problem with the 401 Forbidden on attachments and pictures.

The ROOT_URL is correct. We use a HA PROXY within a openshift as frontend/LB. Since the update from 6.xx to 7.0.9 we see this error.

EDIT: It's not for every attachment, only some are throw the 401 my own I uploaded working, but the one from other Groups not. It looks like it doesn't matter if the users uploaded it himself or from a thrid one of the team. Result is 401, for older Images.

Any idear how we can fix it?