Community

"Invalid File" error when trying to upload an avatar. Affects all users and all image file types.

Bug Reports
  • Dustin FalgoutD
    Dustin FalgoutD
    #1

    I did not notice this while I was staging the site but now that we are live it was discovered that users cannot upload avatars. It gives an "Invalid FIle" error regardless of the file type or size.

    This appears in the terminal log:

    14/2 05:23 [795] - error: /api/user/lots-0-logs/uploadpicture
 Error: [[error:invalid-files]]
    at middleware.validateFiles (/opt/nodebb/src/middleware/middleware.js:108:15)
    at Layer.handle [as handle_request] (/opt/nodebb/node_modules/express/lib/router/layer.js:82:5)
    at next (/opt/nodebb/node_modules/express/lib/router/route.js:110:13)
    at Form.<anonymous> (/opt/nodebb/node_modules/connect-multiparty/index.js:101:9)
    at Form.EventEmitter.emit (events.js:117:20)
    at maybeClose (/opt/nodebb/node_modules/connect-multiparty/node_modules/multiparty/index.js:557:10)
    at endFlush (/opt/nodebb/node_modules/connect-multiparty/node_modules/multiparty/index.js:552:3)
    at WriteStream.<anonymous> (/opt/nodebb/node_modules/connect-multiparty/node_modules/multiparty/index.js:617:5)
    at WriteStream.EventEmitter.emit (events.js:117:20)
    at fs.js:1601:14

    A 500 Error appears in the browser console. Here are the details:

    Remote Address:173.236.248.188:80
Request URL:http://forum.antergos.com/api/user/lots-0-logs/uploadpicture
Request Method:POST
Status Code:500 Internal Server Error
Request Headersview source
Accept:*/*
Accept-Encoding:gzip, deflate
Accept-Language:en-US,en;q=0.8,es;q=0.6
Cache-Control:no-cache
Connection:keep-alive
Content-Length:25331
Content-Type:multipart/form-data; boundary=----WebKitFormBoundarydFjQjP1ZxmA6xrbo
Cookie:express.sid=s%3A_qw_9KMYChOMHC6l0fdDevj1b7LKnqCA.MJKxJamVHDxJ7mUoPypTrOG2AmA34aeXhx2TNlkk9rM
Host:forum.antergos.com
Origin:http://forum.antergos.com
Pragma:no-cache
Referer:http://forum.antergos.com/user/lots-0-logs/edit
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36
x-csrf-token:de8F0HCi-UWwU_dUREF_CLYUdxTJ2ziFC-ig
X-Requested-With:XMLHttpRequest
Request Payload
------WebKitFormBoundarydFjQjP1ZxmA6xrbo
Content-Disposition: form-data; name="userPhoto"; filename="tux_question.png"
Content-Type: image/png


------WebKitFormBoundarydFjQjP1ZxmA6xrbo
Content-Disposition: form-data; name="params"

{}
------WebKitFormBoundarydFjQjP1ZxmA6xrbo--
Response Headersview source
Connection:keep-alive
Content-Length:80
Content-Type:application/json; charset=utf-8
Date:Sat, 14 Feb 2015 05:31:39 GMT
Server:nginx
Vary:Accept-Encoding
X-Frame-Options:SAMEORIGIN
X-Powered-By:NodeBB

    and the response:

    {"path":"/api/user/lots-0-logs/uploadpicture","error":"[[error:invalid-files]]"}

    File uploading works fine for things within the admin like the site logo and category icons. They also work fine with posts. It seems that only the avatars are having the issue. Any ideas on what could be causing this?

    0
  • barisB
    barisB
    NodeBB
    #2

    Please update your upload template so it matches this.

    https://github.com/NodeBB/nodebb-theme-vanilla/blob/master/templates/partials/modals/upload_picture_modal.tpl#L9-L16

    Dustin FalgoutD 1 Reply
    0
  • Dustin FalgoutD
    Dustin FalgoutD
    #3

    @baris Thanks for the quick reply! I made the change but there is no change. The issue is the same 😞

    0
  • barisB
    barisB
    NodeBB
    #4

    Did you restart the forum? I am still seeing the old template in your html

    upload-0b21a79f-7361-4861-bce2-38b47f5fb00f

    Dustin FalgoutD 1 Reply
    0
  • Dustin FalgoutD
    Dustin FalgoutD
    #5

    @baris Yes, I did restart it several times. This is weird. Also, Since this morning I have received emails from almost 20 users saying that the password reset is not working. When they click the email link it tells them "invalid token". When I check the logs I see a csrf error. Could this be related or is it a separate issue? I am beginning to panic a little because I don't know what's the problem nor how to fix it 😟

    Here is the csrf error when the password reset email link is clicked:

    14/2 14:03 [1086] - info: [emailer.mailgun] Sent `reset` email to uid 389
14/2 14:19 [1086] - error: /register
 Error: invalid csrf token
    at verifytoken (/opt/nodebb/node_modules/csurf/index.js:237:11)
    at csrf (/opt/nodebb/node_modules/csurf/index.js:100:7)
    at Layer.handle [as handle_request] (/opt/nodebb/node_modules/express/lib/router/layer.js:82:5)
    at next (/opt/nodebb/node_modules/express/lib/router/route.js:110:13)
    at Route.dispatch (/opt/nodebb/node_modules/express/lib/router/route.js:91:3)
    at Layer.handle [as handle_request] (/opt/nodebb/node_modules/express/lib/router/layer.js:82:5)
    at /opt/nodebb/node_modules/express/lib/router/index.js:267:22
    at Function.proto.process_params (/opt/nodebb/node_modules/express/lib/router/index.js:321:12)
    at next (/opt/nodebb/node_modules/express/lib/router/index.js:261:10)
    at Function.proto.handle (/opt/nodebb/node_modules/express/lib/router/index.js:166:3)
14/2 14:19 [1086] - error: /login
 Error: invalid csrf token
    at verifytoken (/opt/nodebb/node_modules/csurf/index.js:237:11)
    at csrf (/opt/nodebb/node_modules/csurf/index.js:100:7)
    at Layer.handle [as handle_request] (/opt/nodebb/node_modules/express/lib/router/layer.js:82:5)
    at next (/opt/nodebb/node_modules/express/lib/router/route.js:110:13)
    at Route.dispatch (/opt/nodebb/node_modules/express/lib/router/route.js:91:3)
    at Layer.handle [as handle_request] (/opt/nodebb/node_modules/express/lib/router/layer.js:82:5)
    at /opt/nodebb/node_modules/express/lib/router/index.js:267:22
    at Function.proto.process_params (/opt/nodebb/node_modules/express/lib/router/index.js:321:12)
    at next (/opt/nodebb/node_modules/express/lib/router/index.js:261:10)
    at Function.proto.handle (/opt/nodebb/node_modules/express/lib/router/index.js:166:3)
    0
  • barisB
    barisB
    NodeBB
    #6

    Your problems are most likely caused by the out of date templates, since you have a custom theme and vanilla/lavender was updated.

    Try changing back to lavender or vanilla and see if the problems are resolved then you can look at fixing your custom theme.

    0
  • Dustin FalgoutD
    Dustin FalgoutD
    #7

    @baris I went through and made sure my custom theme includes the latest changes from lavender. That corrected many of the issues. However, password resets are still not working. I added an issue to github #2731 Do you have any ideas for what may be causing it? 😕

    PitaJP 1 Reply
    0
  • PitaJP
    PitaJP
    Global Moderator Plugin & Theme Dev
    #8

    @Dustin-Falgout so, the password resets not working, I think, is a know issue

    0

Suggested Topics

  • Alexander CraggsA

    Crash on /search

    Technical Support
    0 Votes
    4 Posts
    2093 Views

    pichaliteP

    @Alexander-Craggs MongoDB, version 2.6 or greater is required

  • NicolasN

    User Profile: Settings

    Solved Bug Reports
    0 Votes
    9 Posts
    3932 Views

    NicolasN

    I have found the issue.
    Previously settings have been used for extra block creation, now it's customSettings
    Changing everything accordingly fixes issue.

  • hekH

    Massive amount of errors in nginx log

    Bug Reports
    0 Votes
    1 Posts
    3275 Views

    hekH

    I must have misconfigured something. But I cannot find out what the problem is. Is anone else experiencing lots of "upstream prematurely closed connection while reading response header from upstream" errors in their nginx log?

    Tried tweaking buffers sizes etc but I see no difference. Get the feeling that nodebb is terminating polling clients connections.

    Running 0.7.0-dev

    bash-4.3# tail -f error.log 2015/04/16 11:08:22 [error] 3682#0: *2132594 upstream prematurely closed connection while reading response header from upstream, client: 80.215.161.163, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291349-3624&sid=RfZHfKKEwNVHpVXoAwaK HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291349-3624&sid=RfZHfKKEwNVHpVXoAwaK", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/1251/power-emission-of-nrf/3" 2015/04/16 11:08:22 [error] 3682#0: *2134758 upstream prematurely closed connection while reading response header from upstream, client: 193.0.242.40, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291692-46449&sid=viXvQ0qO3-W84q8WAwaR HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291692-46449&sid=viXvQ0qO3-W84q8WAwaR", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/category/1/your-project" 2015/04/16 11:08:22 [error] 3683#0: *2134660 upstream prematurely closed connection while reading response header from upstream, client: 193.0.242.40, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291694-5713&sid=prgDiad8lLBmOgMSAwaS HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291694-5713&sid=prgDiad8lLBmOgMSAwaS", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/1018/contest-3d-printed-battery-powered-wall-remote-control" 2015/04/16 11:08:22 [error] 3683#0: *2134796 upstream prematurely closed connection while reading response header from upstream, client: 193.0.242.40, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291697-5940&sid=8YnoBBC_BNP6ebocAwaT HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291697-5940&sid=8YnoBBC_BNP6ebocAwaT", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/796/mysensors-contest-2015/9" 2015/04/16 11:08:22 [error] 3683#0: *2135121 upstream prematurely closed connection while reading response header from upstream, client: 193.109.225.252, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175292021-2931&sid=O8ibWd4vz1Xwl23sAwZ_ HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175292021-2931&sid=O8ibWd4vz1Xwl23sAwZ_", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/305/mysensors-protocol-format" 2015/04/16 11:08:22 [error] 3683#0: *2136215 upstream prematurely closed connection while reading response header from upstream, client: 193.0.242.40, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291704-46206&sid=MqxqCEmwFpQygRUJAwaQ HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291704-46206&sid=MqxqCEmwFpQygRUJAwaQ", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/404/3-in-1-humidity-temp-and-motion/18" 2015/04/16 11:08:22 [error] 3682#0: *2133315 upstream prematurely closed connection while reading response header from upstream, client: 193.109.225.252, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175292024-2940&sid=iBD3mJ_QApuEKMexAwaA HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175292024-2940&sid=iBD3mJ_QApuEKMexAwaA", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/175/open-source-home-automation-raspberry/2" 2015/04/16 11:08:22 [error] 3682#0: *2135389 upstream prematurely closed connection while reading response header from upstream, client: 193.109.225.252, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175292028-2896&sid=FGds-qrKOaArQkHwAwaB HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175292028-2896&sid=FGds-qrKOaArQkHwAwaB", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/175/open-source-home-automation-raspberry" 2015/04/16 11:08:22 [error] 3682#0: *2136281 upstream prematurely closed connection while reading response header from upstream, client: 193.0.242.40, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291713-46237&sid=qdnYQxCy4rSXwKIiAwaU HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291713-46237&sid=qdnYQxCy4rSXwKIiAwaU", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/486/my-2aa-battery-sensor" 2015/04/16 11:08:22 [error] 3682#0: *2136491 upstream prematurely closed connection while reading response header from upstream, client: 94.153.230.50, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=1429175291870-45599&sid=jlQkVDgDcwlbk1yBAwaV HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=1429175291870-45599&sid=jlQkVDgDcwlbk1yBAwaV", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/303/mqtt-broker-gateway/5"

    config.json

    config.json { "secret": "xxx", "bind_address": "127.0.0.1", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "xxx", "database": "1" }, "url": "http://forum.mysensors.org" }

    /etc/nginx/nginx.conf

    user www-data; worker_processes 2; pid /run/nginx.pid; events { worker_connections 1024; # multi_accept on; } http { proxy_buffers 8 16k; proxy_buffer_size 32k; sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; # server_tokens off; server_names_hash_bucket_size 64; include /etc/nginx/mime.types; default_type application/octet-stream; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; gzip on; gzip_disable "msie6"; include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; }

    /etc/nginx/sites-enabled/default

    server { listen 80; server_name forum.mysensors.org; # prevents 502 bad gateway error large_client_header_buffers 8 32k; client_max_body_size 2M; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_redirect off; proxy_buffering off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; gzip on; gzip_min_length 1000; gzip_proxied off; gzip_types text/plain application/xml application/x-javascript text/css application/json; location @nodebb { proxy_pass http://127.0.0.1:4567; } location ~ ^/(images|language|sounds|templates|uploads|vendor|src\/modules|nodebb\.min\.js|stylesheet\.css|admin\.css) { root /usr/mysensors/mysensors-forum/NodeBB/public/; try_files $uri $uri/ @nodebb; } location / { error_page 502 =200 @maintenance; # prevents 502 bad gateway error proxy_buffers 8 32k; proxy_buffer_size 64k; proxy_pass http://127.0.0.1:4567; } location @maintenance { root /opt/nginx/maintanance/; try_files $uri /index.html =503; } }
  • scottalanmillerS

    New Users Default to Admin

    Bug Reports
    0 Votes
    6 Posts
    2636 Views

    scottalanmillerS

    I sure did, let me tell you! 6K users!!

  • DazzuhD

    [Solved] Avatar's refuse to resize.

    Bug Reports
    0 Votes
    15 Posts
    4318 Views

    DazzuhD

    @julian said:

    @Dazzuh If you're running a flavour of Linux, best bet is to install using their package manager... Ubuntu? CentOS?

    oh I tried, according to ubuntu package manager I was already up to date.
    Already figured it out though. Thanks for your help.

| | | |
Copyright © 2023 NodeBB | Contributors