geonerdist Posted February 6, 2018 Share Posted February 6, 2018 (edited) I upgraded to 6.4 recently and starting yesterday I noticed some weird entries in my log, shown below. They only appear in the log when I login to the web UI. the IP of 144 is the computer I'm on right now. I do have the ProFTPd plugin and various dockers, but nothing has changed since I started seeing this. I can pull diagnostics if needed but was mostly curious to see if any one has seen this or may know what it means. My search of the forum and internet revealed nothing that I thought was relevant. Feb 5 18:13:30 Tower nginx: 2018/02/05 18:13:30 [error] 4714#4714: *256266 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"Feb 5 18:13:32 Tower nginx: 2018/02/05 18:13:32 [error] 4714#4714: *256266 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Edited February 6, 2018 by geonerdist Font size Quote Link to comment
geonerdist Posted February 6, 2018 Author Share Posted February 6, 2018 (edited) I did notice there was an update for the ProFTPd plug in so I installed that and logged out of the Web UI and logged back in and the log shows this now: Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "logout" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "logout" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"Feb 5 18:20:01 Tower nginx: 2018/02/05 18:20:01 [error] 4714#4714: *257229 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Edited February 6, 2018 by geonerdist Font size Quote Link to comment
ljm42 Posted February 6, 2018 Share Posted February 6, 2018 From the release notes for 6.4.1: rsyslogd: suppress nginx message 'user "logout" was not found in "/etc/nginx/htpasswd"' Not sure about "ftpuser" though, could be an issue with the plugin. I'd recommend updating to 6.4.1 and if the issue persists, upload your diagnostics. Be sure to read the update notes here: 1 Quote Link to comment
geonerdist Posted February 7, 2018 Author Share Posted February 7, 2018 After upgrading the issue persists. Prior to the upgrade I disabled mover logging and the server has only been up for less than 13 minutes when I downloaded my diags. The errors appeared at 19:19. Thanks for the reply @ljm42. I was thinking it was an issue with the plugin except for the fact that this error appears only when I log in/out of the web UI. tower-diagnostics-20180206-1920.zip Quote Link to comment
ljm42 Posted February 7, 2018 Share Posted February 7, 2018 @SlrG , do you have any ideas on this? I'm not sure why the "ftpuser" would be trying to access the webgui, it could just be a weird artifact of how logout was implemented. I doubt it is a serious problem. 1 Quote Link to comment
SlrG Posted February 8, 2018 Share Posted February 8, 2018 Thank you for the info. I'm not on 4.6.1 yet and have no security on the webgui enabled. So I did not experience this problem yet. I'll upgrade and try to replicate it. What I can say however is, that my ProFTPd plugin creates no user ftpuser, it is only a keyword the user has to enter in the description field in unRAIDs user creation dialog to identify users that should only be able to login by FTP and or should be jailed into the given directory. @geonerdist Do you have an user ftpuser defined as unRAID user or only have users with this keyword in the description field? Does the error go away if you uninstall the ProFTPd plugin? 1 Quote Link to comment
SlrG Posted February 8, 2018 Share Posted February 8, 2018 @ljm42 @geonerdist On my system I can't replicate the problem. Did upgrade do 6.4.1 and set a password for root to enable webgui login security. Logging in and out multiple times does not result in any errors in the log. Maybe the answers to my questions from above give me an idea what is going wrong. Quote Link to comment
geonerdist Posted February 9, 2018 Author Share Posted February 9, 2018 @SlrG I haven't done any of the extra security stuff that's been enabled in 6.4. I have always had a password set for the root user. I only have two users root and mine, there is no ftpuser. Ftpuser is just a keyword added to my personal user account to enable that to login to my FTP share. I'm planning on removing the ProFTPd plugin this weekend to see what might happen. Quote Link to comment
geonerdist Posted February 24, 2018 Author Share Posted February 24, 2018 I finally got around to testing this out...I use my FTP a lot more than I thought when I first set it up. Anyways I first disabled the server, then disabled ProFTPd, the uninstalled the plugin and still get this error when logging in to the UI. Baffling...but as you all have said I don't think it's a problem at all...just looks scary on the System Log with all that red. Quote Link to comment
SlrG Posted February 24, 2018 Share Posted February 24, 2018 (edited) @geonerdist Do you have the ftpuser keyword in the comments for the root user, too? Can you try to remove the ftpuser keyword from all your user accounts comments while the ProFTP plugin is uninstalled? Then reboot. Does this solve the problem? If not, can you try to remove your personal, user(s) reboot and recreate it(them) without the ftpuser keyword? If both things do not solve your problem, I can't think of a reason how my plugin could be the cause. Edited February 24, 2018 by SlrG Quote Link to comment
geonerdist Posted April 7, 2018 Author Share Posted April 7, 2018 @SlrG Apologies for the lack of response. So far I have not seen this error lately. But it might being mask by some ACPI errors in the log that the Gen8 MicroServer is prone to, so that is my current project. But I'll be coming back to this soon. I'll give those a shot when I come back around to this. Quote Link to comment
SlrG Posted April 7, 2018 Share Posted April 7, 2018 No problem. Let me know if you find anything. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.