If you mean that people can see a listing of the directories. Than you may have an error in your .htaccess.

It should be disabled: see https://github.com/Elgg/Elgg/blob/1598cc34dfec71bff969563c2c7b070e616bb2a5/install/config/htaccess.dist#L6-L7

Indeed. Fixed now. Thanks.

Use this version https://github.com/hypeJunction/Elgg3-hypeDropzone/archive/refs/tags/6.0.0.zip

I tried it, but unfortunately it does not fix the problem. Do I need to edit any file in files plugin ?

Just tested it and this plugin works very well as is without any modifications.

• Deactivate the existing hypeDropzone plugin.
• Remove this folder /mod/hypeDropzone from your server.
• Run 'Flush the caches'.
• Download https://github.com/hypeJunction/Elgg3-hypeDropzone/archive/refs/tags/6.0.0.zip and unzip it to /mod/hypeDropzone
• Activate plugin
• Go to Files and try to Upload a file

Elgg does not use SMTP to send email notifications. Only if you use some additional plugin it might be that your Elgg site sends the mails via SMTP. In this case the SMTP settings would have to be changed in the plugin settings of this plugin.

What exactly do you mean by the transfer to a new server location? Has only the server changed with the domain name being the same? What is used as site email of the site (see Basic Settings)? If the domain name has changed and the site email address is from the old domain the server might deny sending the emails. If the domain name has not changed (and site url etc. also hasn't to be changed) the question is if the email account used as site email exists on the new server and if the MTA (mail transfer agent, e.g. Postfix) is set up on the server. The MTA must be set up for sending of mails to work as Elgg itself relies on it and has no email server capabilites itself.

You could know more information using the bundled plugin 'Elgg Developer Tools': add  unknown GUIDs (157048, 37815, 157047 etc) in Tools -> Entity explorer via Administration to know what going wrong.

Advice: don't use the outdated Elgg version. Upgrade it.

I think that's perfectly alright. Nothing to worry about.

As I normally don't use the log browser plugin at all (using my No Logging plugin to prevent Elgg log entries from being created as these log entries seem not useful to me at all) I had to check the logbroser entries in a test installation first and I see the same kind of entries without anything in the User and UserGUID columns. Some log entries just won't get anything for these columns.

Elgg 1.8 is no longer supported (for years). Might be that a newer version of Elgg works better / without issues over SSL. You could also try https://elgg.org/plugins/782028 which has a newer version of the Tinymce editor than the version included in Elgg 1.8. Maybe this version works also fine over SSL if it's only an issue with the Tinymce editor itself. Nonetheless, updating to a newer version of Elgg is something you should keep in mind.