surviving404

Yes the images open in lightbox on clicking (in original size),

I am glad you worked it out 🙂

Hey,

What is the error that you see?
Were you able to upload images? If No, Can you please log into the docker container and check the permissions in WordPress root folder?

Hey,

It indeed seems like the site is being attacked when someone trying to use existing username attempted to log in.
Username can be seen in many ways and bots scan sites to get usernames either from posts and author archives. Posts have author name in them.

I created another 2 test accounts (Admin role) and did absolutely nothing with them. I did login once with one account and the other one was never used for nothing. So these 2 accounts do not appear in the full logs at all

Because those users do not have any posts or pages created, and no content linked to them.

Though Exposure of usernames in not considered a security issue.
https://make.ww.wp.xz.cn/core/handbook/testing/reporting-security-vulnerabilities/#why-are-disclosures-of-usernames-or-user-ids-not-a-security-issue

Still, To prevent login attempts, you can use security plugins like Wordfence.
Publish posts with the users that are not administrators

More security measure you can take to hide your usernames, that you can read here https://melapress.com/user-enumeration-wordpress/

Hey,

For calculation I think you will have to go with conditional form approach.
If you explain what type of calculation it would be, it might be helpful to suggest more effective solution. 🙂

Have you tried changing to default theme (twenty-twentyfive or twentyfour)?

Please try doing that and check if the footer reappears, if it does then it probably is the issue with the theme.

@threadi Well…

This error I think is not because of the theme, since it persists even after I change the theme to default theme or even other like kadence, and even on different WordPress installation.

Though I was unable to pinpoint the real reason for this.

Hey,

Cloudfront behaviour will need path pattern set for /wp-content/* & /wp-login.php & /wp-includes/* also along with the one ones you have, and also if you plan to add some contact form on your site you will have to add that page path also in behaviour pattern.

This video https://www.youtube.com/watch?v=-EXS9M6yMcA
and this blog https://aws.amazon.com/blogs/startups/how-to-accelerate-your-wordpress-site-with-amazon-cloudfront/ on AWS docs will help you to set those up.

Do reach out if you face more problem(s) since it is a tedious process. 🙂

S.D.