Closed TheReal1604 closed 7 years ago
I do see the following in the logs after upgrading to 0.57.0
from 0.56.0
:
[34mI20170705-10:51:19.778(0) Exception while invoking method 'ufsComplete' InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records. at Object.Future.wait (/app/bundle/programs/server/node_modules/fibers/future.js:449:15) at [object Object].Meteor.methods.ufsComplete (/app/bundle/programs/server/packages/jalik_ufs.js:818:24) at [object Object].methodsMap.(anonymous function) (/app/bundle/programs/server/packages/rocketchat_lib.js:1028:26) at [object Object].methodMap.(anonymous function) (packages/rocketchat_monitoring.js:2731:30) at maybeAuditArgumentChecks (/app/bundle/programs/server/packages/ddp-server.js:1823:12) at /app/bundle/programs/server/packages/ddp-server.js:905:20 at [object Object]._.extend.withValue (packages/meteor.js:1122:17) at /app/bundle/programs/server/packages/ddp-server.js:904:41 at [object Object]._.extend.withValue (packages/meteor.js:1122:17) at /app/bundle/programs/server/packages/ddp-server.js:903:46 at [object Object]._.extend.protocol_handlers.method (/app/bundle/programs/server/packages/ddp-server.js:876:21) at /app/bundle/programs/server/packages/ddp-server.js:755:85 - - - - - at Request.extractError (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/services/s3.js:577:35) at Request.callListeners (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:105:20) at Request.emit (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:682:14) at Request.transition (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/state_machine.js:14:12) at /app/bundle/programs/server/npm/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:684:12) at Request.callListeners (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at Request.emit (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:682:14) at Request.transition (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/state_machine.js:14:12) at /app/bundle/programs/server/npm/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/request.js:684:12) at Request.callListeners (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at callNextListener (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/sequential_executor.js:95:12) at IncomingMessage.onEnd (/app/bundle/programs/server/npm/node_modules/aws-sdk/lib/event_listeners.js:269:13) at emitNone (events.js:72:20) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:923:12) at nextTickCallbackWith2Args (node.js:511:9) at process._tickDomainCallback (node.js:466:17)
Excuse me for the garbled format, but that is how it presented itself to me in the log.
The issue persists in 0.57.1
.
I decided to try downgrading back to 0.56.0
(which sported a fully functional Minio integration) but any uploads results in the following:
When I re-enabled file uploads I restarted the server, but it still only yielded the same result as shown in the screenshot.
The log claims InvalidAccessKeyId
(exactly the same as shown in this comment).
I do not know what is wrong. There has been no changes on my Minio instance -- it runs fine as usual.
S3 file upload (with Minio, to be clear) is now working with latest version (i.e 0.57.2
) but all avatars were missing and the users had to re-upload them. Other than that...well, it is working fine ;)
Thanks, team!
Rocket.Chat Version: 0.57.0 Running Instances: 1 DB Replicaset OpLog: yes
Since the update the support for the minio file upload backend (as used as aws s3 storage) seems to be broken:
It seems that the rocket.chat instance does the request on another way since the update and gets an http code 403. Maybe a possible direction: I doesnt see the requests on my minio instance anymore. Maybe the URL is some kind of hardcoded?
It is configured like described in the docs: https://rocket.chat/docs/administrator-guides/file-upload/minio
Any idea?