Skip to content
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

File-Upload not working in Version 4.0.3 #1261

Closed
worlword opened this issue Oct 23, 2018 · 9 comments

Comments

@worlword
Copy link
Contributor

commented Oct 23, 2018

I've tried to send a File in a Single-User-Chat in converse.js 4.0.3. I used the paperclip symbol in the toolbar to open the dialog and selected a file. After that the progress-bar for the upload showed up. And that's it. Nothing else happens. I can still send Text afterwards and also try to upload new files (same result).

System-Information:
XMPP-Server: eJabberd 18.04
Apache:
Server version: Apache/2.4.6 (CentOS)
Server built: Apr 20 2018 18:10:38
Test-File:

  • HTML-File with "Hello World" as content
  • Size 11 Bytes
    Browser:
  • Chrome Version 69.0.3497.100 (Offizieller Build) (64-Bit)

The Browser-Console-Log shows an Error upon PUT-Request (see later screenshots) and atfer that there are some promise-Errors:
converse_4_0_3_promise_error_during_fileupload html
Those Errors propably cause the progress-bar to stay forever.

The PUT-Request:
dateiuploadversion4_0_3

The actual Response says:
dateiuploadversion4_0_3_response

When I use git to switch back to converse.js Version 4.0.1 and try that version, it works. The following is a screenshot of the same request with 4.0.1:
dateiuploadversion4_0_1 html

I've tried with several diffrent files: .png, .jpeg, .mp4, .html, .txt. They all work with 4.0.1 but not with 4.0.3. I also tried 4.0.2 shortly. Here the same error occurs.

@laszlovl

This comment has been minimized.

Copy link
Contributor

commented Oct 24, 2018

Can confirm, although it was working properly for me in 4.0.2 as well.

@jcbrand

This comment has been minimized.

Copy link
Member

commented Oct 24, 2018

@worlword Would it be possible to give me a test account? File uploads work for me in 4.0.3 on my own server.

@licaon-kter

This comment has been minimized.

Copy link
Contributor

commented Oct 24, 2018

Seeing the same on ejabberd 18.09

@jcbrand

This comment has been minimized.

Copy link
Member

commented Oct 24, 2018

Well, if any of you can give me a test account I can check.

You can contact me here: http://opkode.com/contact.html

@jcbrand jcbrand closed this in e0f0617 Oct 24, 2018

@jcbrand jcbrand added this to the 4.1.0 milestone Oct 24, 2018

@jcbrand jcbrand added bug and removed investigation-required labels Oct 24, 2018

@licaon-kter

This comment has been minimized.

Copy link
Contributor

commented Oct 25, 2018

Updated to HEAD, still error 413, but now ejabberd is rejecting the upload: https://gist.github.com/licaon-kter/8e596c86639ce8b3474b674dcfd93529

As others above, this works fine at least in 4.0.1.

/LE: ejabberd.yml: https://gist.github.com/licaon-kter/eb0263c2f7feb232ca5021c9bff0730f

@jcbrand jcbrand reopened this Oct 25, 2018

@jcbrand

This comment has been minimized.

Copy link
Member

commented Oct 25, 2018

@licaon-kter Yes, I heard last night in the chat. I'm not sure what the issue is, it's working for me locally with Prosody.

A test account would help me reproduce/debug.

@mightymop

This comment has been minimized.

Copy link

commented Oct 26, 2018

i can confirm this bug on openfire servers too
can not upload files.

1st Error on my Server with converse js Version from cdn:

Uncaught (in promise) Error: Invalid arguments at filesize...
err1

2nd error on converse js website logged in on my server:

Error: Invalid arguments filesize.js:57

bildschirmfoto vom 2018-10-26 07-05-01

@worlword

This comment has been minimized.

Copy link
Contributor Author

commented Oct 26, 2018

Hallo. Sorry for the late replay I was very busy the last Days.
Sadly I cannot give a test-account because it is not possible to reach the server from the outside.

Maybe I can look into it on the weekend to find out what causes the bug.

@laszlovl

This comment has been minimized.

Copy link
Contributor

commented Oct 26, 2018

Can confirm it's still broken for me in master as well, using Ejabberd 18. I have a test account/setup ready at request.

jcbrand added a commit that referenced this issue Oct 26, 2018

@jcbrand jcbrand closed this Oct 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.