-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: TypeError: OCA\UserStatus\Controller\UserStatusController::__construct()
Argument #3 ($userId) must be of type string, null given
#42156
Comments
OCA\UserStatus\Controller\UserStatusController::__construct()
Argument #3 ($userId) must be of type string, null given
This comment was marked as resolved.
This comment was marked as resolved.
A few days earlier I got this Error which may be related, the user name is redacted:
Nextcloud Hub 7 (28.0.1) |
Same here. I tried reinstalling nextcloud but the problem persists. Fix? Installation method Community Manual installation with Archive Nextcloud Server version 28.0.1 Operating system Ubuntu 23.04 PHP engine version PHP 8.2 Bug description TypeError: OCA\UserStatus\Controller\UserStatusController::__construct(): Argument #3 ($userId) must be of type string, null given at /var/www/nextcloud/apps/user_status/lib/Controller/UserStatusController.php#53 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Neither the null string error nor the duplicate entry error has reoccurred on my system. I am not using a proxy. I am also using Apache |
Same problem after installing 28.00. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Problem has not appear anymore since I have deactiviated the Cache. |
This comment was marked as resolved.
This comment was marked as resolved.
"Cache Assets" should not be enabled with Nextcloud in NPM. NPM has a very aggressive cache configuration: It serves no real purpose with Nextcloud. Typically a reverse proxy is colocated alongside Nextcloud Server (i.e. not on the other side of the world from it) and the browser caches the assets anyhow. Having that option enabled will likely lead to numerous problems with Nextcloud because it ignores managed headers and intentional cache busting. |
This comment was marked as resolved.
This comment was marked as resolved.
I do have the same error message as well: They occurred the last time on 4th, 6th and 10th of March.
The last error I have in my log is from 11th of march. I did update the container on March 13th and have no problems since. |
Also an issue on NC 29 RC1
|
Got it again on March 27th with NC 28.0.4 -> unfortunately still present |
Same problem here with NC 28.0.5 and Apache with PHP 8.2 |
This is affecting me as well (28.0.5, manual install in a VM following the published installation instructions, updated from 27):
Is this the same bug as #25071? |
Same issue here. Nextcloud docker image and nginx proxy manager. Worked for a year without issue and since the last NC update, first circles broke and killed the whole instance and now that. I dont have block common exploits, cache assets or websockets enabled, I do have custom locations caldav and carddav enabled as well as forcessl, http/2 support and HSTS, no HSTS subdomains. Configuration here:
|
This comment was marked as resolved.
This comment was marked as resolved.
@pktiuk Can you confirm Cache Assets is off (in NPM)? Some people here are triggering this bug due to that (which is a misconfiguration). Others... not sure. |
For those of you seeing these requests come in via your browser - e.g.
Can you check your browser inspector and under the Network tab see what Request Headers are being sent during these failing requests? They'll likely be easy to spot under your Network tab since they'll be red due to a 500 error. Please also check Administration settings->Overview and make sure you're not getting any other errors or warnings. |
first off: these two errors do happen at almost the same time: This one happens, but does not seem to be timing related: then these 3 are almost at the same time: I do use NC on 2 seperate PCs view browser (both firefox) and on the iOS app. because I currently do not have an error, here are the headers I can show you: Btw I do not have to re-login on the iOS app, only in the browser, and only every couple of days / weeks. Did never have the probling with NC27 and before, only since NC28 and NC29 did not fix it :( |
Thanks, @naelfe. This confirms my suspicion (at least in your case). That first error is closer to the cause than the user status error this issue has been focused on so far. So that is helpful. The user status TypeError should only occur if the user session is already somehow messed up. Which is what the first error immediately preceding it is indicating. Now we know to not spend any time looking at the user status code because that's not where the problem is. Still not sure of the root cause, but it gets us closer to the origin. And it's quite possibly related to a couple other open Issues (or at least the work on them may turn up something useful here). Of course the ability to reproduce would be ideal, but we work with what we've got sometimes. :-) |
Could this be related to the user_external app maybe? |
Unfortunately I do not have it enabled :( Since we are already at that topic- apps that I once had installed and are currently disabled: The only two non-featured apps I do have active are: also currently using update / edit: |
Error in NC 20.0.4 RC1
|
Nextcloud 30.0.1 RC2
|
Bug description
Error on NC 28 RC4
TypeError: OCA\UserStatus\Controller\UserStatusController::__construct(): Argument #3 ($userId) must be of type string, null given at /var/www/nextcloud/apps/user_status/lib/Controller/UserStatusController.php#52 --Steps to reproduce
Note Sure
Expected behavior
Not Sure
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: