Ah, yes, that is potentially a stumbling block... port property is optional, if not specified, NodeBB will listen on port 4567. However the url property is the one that is referenced by NodeBB, and is used as the canonical reference to itself... so when somebody asks your forum what it is to be called, NodeBB will respond back with the value in url, so the port is required if you are accessing your forum with port number in url.
v0.9.3: Error encountered while uploading a user profile picture
rod last edited by rod
I attempted to upload a user profile picture and received the following error after the file upload bar went to 100%:
error uploading, code : 502
Looking through my Nginx log files I see this error logged:
2016/02/03 08:26:25 [error] 962#0: *12317 connect() failed (111: Connection refused) while connecting to upstream, client: [MY IP ADDRESS], server: myForumHere.com, request: "GET /socket.io/?EIO=3&transport=polling&t=1454513183873-9 HTTP/1.1", upstream: "http://127.0.0.1:4568/socket.io/?EIO=3&transport=polling&t=1454513183873-9", host: "myForumhere.com", referrer: "https://myForumHere.com/user/myUserName"
(I redacted my client IP address, my forum name, my forum URL, and my actual username.)
I am using the AmazonS3 plugin but I am able to upload the same image into a new topic. Any ideas on what I should check for the root of the problem?
EDIT: Adding additional error found in log:
I found this error in my error logs above the one I previously posted:
2016/02/03 08:26:10 [error] 962#0: *12317 upstream prematurely closed connection while reading response header from upstream, client: [MY IP ADDRESS], server: myForumHere.com, request: "POST /api/user/myUserName/uploadcover HTTP/1.1", upstream: "http://127.0.0.1:4568/api/user/myUserName/uploadcover", host: "myForumHere.com", referrer: "https://myForumHere.com/user/myUserName"
As before I edited [MY IP ADDRESS], myForumHere.com and myUserName.
Where on the filesystem do user's profile pictures reside? I want to confirm that the user that Nginx runs under has write access.
@rod It wouldn't be Nginx, it would be NodeBB that needs write access.
@PitaJ Ok. And yes, the linux user that NodeBB runs under owns all of the directories.
After further testing this problem appears to be related to the
nodebb-plugin-amazons3plugin. After I disabled it I was able to upload a user profile picture.