nodeham

joined 3 years ago
sorted by: new top controversial old
Script kiddies need lives in c/[email protected]
Script kiddies need lives in c/[email protected]
[–] [email protected] 1 points 3 days ago (1 children)

One question. Are the dashboard logs derived from the web server logs or directly from the nodebb code? I assume directly.

Script kiddies need lives in c/[email protected]
[–] [email protected] 1 points 3 days ago (1 children)

Well, I wasn't posting looking for technical information but now you have me curious :).

Looking at the logs, they strongly suggest automated bot activity. Hits from Googlebot and other search crawlers WordPress vulnerability scanners Automated scanning tools like ZGrab

Are these triggering login attempts either by mistake or as part of their crawling process? Googlebot, for example, accesses various URLs, including login pages, and might cause login events.

Many of the requests are targeting /wp-admin/setup-config.php, /wordpress/wp-admin/setup-config.php, /xmlrpc.php, /wlwmanifest.xml, and similar WordPress-related URLs.

Since it's not a WP site, are these requests resulting in redirects or 301 responses, but getting counted in access logs that result in the dashboard stats?

Script kiddies need lives in c/[email protected]
[–] [email protected] 1 points 3 days ago (1 children)

Yes but aren't those usually script kiddies? The number of unique visitors is only 202 while the login attempts are nearly 15K for yesterday alone.

2
Script kiddies need lives (community.nodebb.org)
 

No problems with nodebb, just an observation of so many people wasting their lives trying to hack others. Some having the potential to be highly skilled and well paid folks but instead spend their time trying to hurt others.

I put a site online just to test a few things. It's not advertised or mentioned anywhere yet but look at the stats. Lots of hits from bots, most presumably looking for Wordpress sites. I just thought it was interesting and wanted to share.

979562de-957f-42c0-8f4b-28e2e7aba0c4-image.png

410 gone using API in c/[email protected]
[–] [email protected] 1 points 6 days ago

I ended up rebuilding as there seem to be too many goofy things going on. Now it seems fine so have no idea what went wrong. It is acting normal now.

One odd thing is that I'm using postgres with my install and it seems to be legacy based. I've been using mysql for many years and the default mongo db with nodebb so it's the first time I'm using postgres.

Markdown settings missing in c/[email protected]
[–] [email protected] 1 points 1 week ago

Jeez I feel stupid for posting this. Of course, I forgot to rebuild that time.

Thanks for your help.

1
Markdown settings missing (community.nodebb.org)
 

I'm trying to find how I can enable Parse Markdown in API posts so I go to Extend, Plugins, Active and click on Settings for the markdown plugin.

That leads me to;

Not Found You seem to have stumbled upon a page that does not exist.

Am I doing something wrong or is there a bug?

410 gone using API in c/[email protected]
[–] [email protected] 1 points 1 week ago

Single at the moment but with plans to go multiple if traffic warrants it. I'll do some debugging as suggested and report back.

410 gone using API in c/[email protected]
[–] [email protected] 1 points 1 week ago

it's not public yet no.

The Post Exists but Isn't Loading in the UI. To test, I refresh the post in my browser and it goes 410. When I add api into the url, I see the post but it's all code. A refresh does not get the 410.

1
410 gone using API (community.nodebb.org)
 

I'm using the nodebb API to create posts and update them. The user is fully allowed to post as the API authenticated user. There are no limitations or auto removals set in the nodebb forums settings.

I can go to the category and click on the post and see it. I can move away from the category and go again and I see the post. The only time it goes 410 is when I refresh the browser while viewing the post.

I'm told it could be the nodebb cache causing this but if that is the case, how can I prevent this from happening as I certainly don't want to disable cache. Posts should never show 410 gone when they are in fact still there so what's going on?