• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Can't upload profile pics on Windows server install

Scheduled Pinned Locked Moved Bug Reports
windowsuploadprofile
11 Posts 3 Posters 5.4k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • barisB Offline
    barisB Offline
    <baris> NodeBB
    wrote on last edited by
    #2

    That error seems to be coming from the gm module, at
    https://github.com/NodeBB/NodeBB/blob/master/src/image.js#L18 and
    https://github.com/NodeBB/NodeBB/blob/master/src/image.js#L23, not sure how compatible they are on windows, you can try commenting out those resize lines and see if uploads work.

    1 Reply Last reply
    0
  • QuylaaQ Offline
    QuylaaQ Offline
    Quylaa
    wrote on last edited by
    #3

    I commented out those lines and now I get this:
    Pzq6K3f.png

    1 Reply Last reply
    0
  • D Offline
    D Offline
    derrg
    wrote on last edited by
    #4

    Have you tried running node from a command prompt in Administrator mode ('Run as Administrator')?

    1 Reply Last reply
    0
  • QuylaaQ Offline
    QuylaaQ Offline
    Quylaa
    wrote on last edited by
    #5

    I RDP in as Administrator (not very secure, I know, we're going to disable it before going live), so the command prompt runs as admin every time. I tried changing the permissions of the folder it says in the error, but that didn't change anything. I even ran a fresh install of NodeBB, but that had no effect either. At this point what we're gonna do is just run it on a small Linux box.

    1 Reply Last reply
    0
  • D Offline
    D Offline
    derrg
    wrote on last edited by
    #6

    I can't blame you; Windows can be pretty finicky sometimes. If you have UAC enabled, I think you might still have to specify that you want to run your command prompt in Administrator mode. I'd double check that just to make sure.

    I found someone who was having somewhat similar problems with node's GraphicsMagick (gm) plugin on StackOverflow and it looks like their solution involved changing require('gm').subClass({imageMagick:true}) to require('gm'), as well as running node from Administrator mode.

    1 Reply Last reply
    0
  • QuylaaQ Offline
    QuylaaQ Offline
    Quylaa
    wrote on last edited by
    #7

    Well now all I get is a "spawn ENOENT" error, which I fixed on the Linux machine by installing imagemagick through apt. Unfortunately, installing it on Windows didn't work.

    1 Reply Last reply
    0
  • D Offline
    D Offline
    derrg
    wrote on last edited by
    #8

    Looks like a permissions error, but their solution is to use require('gm').subClass({ imageMagick : true}).

    Maybe Linux is the answer for you after all! 😆

    1 Reply Last reply
    0
  • QuylaaQ Offline
    QuylaaQ Offline
    Quylaa
    wrote on last edited by
    #9

    Yea, I'm just gonna stick with hosting it on the Linux server. Thanks anyway!

    1 Reply Last reply
    0
  • D Offline
    D Offline
    derrg
    wrote on last edited by
    #10

    I'll try to reproduce the error and see if I can't fix it.

    1 Reply Last reply
    0
  • D Offline
    D Offline
    derrg
    wrote on last edited by derrg
    #11

    I've managed to reproduce the issue on Win2k8R2. It's coming from ImageMagick not being installed/configured correctly.

    reproduced.png

    These are the steps I took to fix the issue:

    1. Go out and install the latest version of ImageMagick

    2. After running the installer make sure that you close the command prompt from which you are running NodeBB.

    3. Open a new command prompt and rerun node app.js

    The problem should be fixed! 🙂resolved.png

    1 Reply Last reply
    2

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development