Forum Activity for @jrblack1175

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

Seems like the skin is throwing some invalid OWASP errors. And to be fair, I have installed other software with css styles, and don’t have the same problem.

But, thanks for all your help.
updated by @jrblack1175: 04/25/20 09:21:35AM

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

I can access my server error logs:

GET /jamroom/core/skin_admin/style/skin=jrElastic2/file=admin_menu.css/section=advanced HTTP/1.0

GET /error_docs/styles.css HTTP/1.0

GET /jamroom/profile/get_pulse_counts/__ajax=1 HTTP/1.0

[client 212.102.50.92] ModSecurity: Warning. Pattern match "(?i)\\\\b(?:s(?:tyle|rc)|href)\\\\b[\\\\s\\\\S]*?=" at REQUEST_COOKIES:jr_location_url. [file "/etc/apache2/modsecurity.d/rules/owasp_modsecurity_crs_3-plesk/REQUEST-941-APPLICATION-ATTACK-XSS.conf"] [line "814"] [id "941150"] [rev "2"] [msg "XSS Filter - Category 5: Disallowed HTML Attributes"] [data "Matched Data: style/skin= found within REQUEST_COOKIES:jr_location_url: https://blissfulignorance.com/jamroom/core/skin_admin/style/skin=jrElastic2/file=admin_menu.css/section=advanced"] [severity "CRITICAL"] [ver "OWASP_CRS/3.0.0"] [maturity "1"] [accuracy "8"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-xss"] [tag "OWASP_CRS/WEB_ATTACK/XSS"] [tag "WASCTC/WASC-8"] [tag "WASCTC/WASC-22"] [tag "OWASP_TOP_10/A3"] [tag "OWASP_AppSensor/IE1"] [tag "CAPEC-242"] [tag "paranoia-level/2"] [hostname "blissfulignorance.com"] [uri "/jamroom/core/skin_admin/style/skin=jrElastic2/file=admin_menu.css/section=advanced"] [unique_id "XqKB@2FlBtC7TcJy@diYUQAAAA8"], referer: https://blissfulignorance.com/jamroom/core/skin_admin/style/skin=jrElastic2

[client 212.102.50.92] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/etc/apache2/modsecurity.d/rules/owasp_modsecurity_crs_3-plesk/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "57"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 5)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "blissfulignorance.com"] [uri "/jamroom/core/skin_admin/style/skin=jrElastic2/file=admin_menu.css/section=advanced"] [unique_id "XqKB@2FlBtC7TcJy@diYUQAAAA8"], referer: https://blissfulignorance.com/jamroom/core/skin_admin/style/skin=jrElastic2

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

I navigated to the media directory. It exists, and all kinds of files are in there, including my custom header file. So, it makes 0 sense that there's no write capabilities to that file. Clearly, when I used another part of the UI to upload those new files, it was able to write to that folder and put the images in there. So, it's not my server. It's a bug.

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

Same problem with Elastic2. I try to go to a different .css file in the drop-down list and get blocked. I'm done.

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

Um, I don't need to navigate around the block by installing a third browser. I need to be able to update the style in the template without getting blocked from my server - in 2 different browsers, btw. On multiple occasions.

And if that's not a possibility - to update the COLOR OF THE TEXT on a skin, then there's some serious issues with that skin... How about I try to see if I can replicate the same error in another skin? Or maybe you can tell me which skin works with this software - since Follow Me wasn't a good choice because "it's not really for blogs" and Lucid isn't a good choice because it has a fatal error when trying to change the color of text.

Adding Multiple TXT files to a Blog post

Installation and Configuration

That might work. It means people couldn’t comment on it in between.

The use case is: I’m an author; I wrote the first chapter to my story. I upload it to the blog. About 2 weeks later, I have completed a 2nd chapter. I edit and add that to my blog post. Several weeks after that, I add a 3rd chapter.

Hopefully, people have read and interacted with the chapters as I uploaded them...

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

I sent the requested info to the email... Any luck? Did you reproduce the error?

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

I don’t know how to give you a url to my admin console w/o credentials?

Lucid Skin Error gets my server blocked on Chrome and Safari

Installation and Configuration

Hello. So, after the exchange about FollowMe not being a great skin for blogs, I went with a blogging skin, Lucid. Installed it, have been working with it... I am using the dark style of the skin and wanted to find out where the color for the font on the blog post information is - because it's dark gray on a black background. This has happened to me twice tonight... I scrolled on the Skin Style page - from the admin_log.css and tried to go to "base.css"

I get a 403 error and am then banned from going to my own site for a few hours, using Chrome (I can still get there using Safari). Here is the error I receive, when I try to circumvent the web address and just go straight to the IP addrress:

74.208.166.135 normally uses encryption to protect your information. When Google Chrome tried to connect to 74.208.166.135 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 74.208.166.135, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit 74.208.166.135 right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later."

I reinstalled an SSL certificate earlier and turned off the "force to https" and turned it back on, which either fixed it or coincided with the period of time that Chrome blocked/banned me. But, considering this has happened twice when I did the same thing using the Jamroom software, there has to be something odd happening when I try to navigate to other parts of the Lucid style information...

And when I tried using Safari to navigate to any other *.css file in the list, I got the 403 error and I'm now unable to get to my website via Safari. I can, however, still access my server console - which, I can't do in Chrome.

So, I'm unable to do anything on my website for the rest of the night, I guess.

Thanks.
updated by @jrblack1175: 04/25/20 08:38:52AM

Adding Multiple TXT files to a Blog post

Installation and Configuration

@Paul, I was able to get 2 files uploaded and can view them, now!

It does seem that in order to enable more files to be uploaded, I'll have to go create a lot more fields, though, as there's no ability to +add+ files after the 2, just replace.

I will also go check out the information on the importer stuff. I have a 500MB DB that I'm exporting. I can backup the db and take a bunch of forums out that I don't care as much about - but I'm not sure about exporting to a CSV file.... What those limitations might be.

If the custom work and the importers will bring over the content with the html coded posts displaying correctly, and the attachments in tact, then it'd be worth it. If not, I'm stuck in the same place I am, now, and may as well just manually bring over select pieces of content...as "just another free service I provide" (for some reason...)

As an example, this is what I'm left with on many of my old forum posts: https://blissfulignorance.com/phpBB3/viewtopic.php?f=76&t=9615&sid=93423dab57ec7005a49f9daf242aa5bc