• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Website registration check not working with ubuntu 22

Eprinsa

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
18.0.56
When entering this option we do not see any records, even though we have configured the tool to launch automatically daily at 06:25 every 60 minutes.
When trying to launch the manual check, the following error appears:

logparser failed: ERROR: Failed to construct 'audit-modsec-with-ts' step
[2023-08-17 13:24:14,718] logparser INFO: This exception happened at:
Traceback (most recent call last):
File "pipeline.py", line 184, in _build_from_config
self.steps[step_name] = Step(step_name, step_config)
File "pipeline.py", line 35, in __init__
step_impl = step_class(name=name, **config)
File "steps/grok.py", line 66, in __init__
self.grok = Grok(grok, custom_patterns=custom_patterns or {}, type_caster=_type_caster)
File "pygrok/pygrok.py", line 63, in __init__
self.regex_obj = re.compile(py_regex_pattern)
File "/usr/lib/python3.10/re.py", line 251, in compile
return _compile(pattern, flags)
File "/usr/lib/python3.10/re.py", line 303, in _compile
p = sre_compile.compile(pattern, flags)
File "/usr/lib/python3.10/sre_compile.py", line 788, in compile
p = sre_parse.parse(p, flags)
File "/usr/lib/python3.10/sre_parse.py", line 955, in parse
p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
File "/usr/lib/python3.10/sre_parse.py", line 444, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
File "/usr/lib/python3.10/sre_parse.py", line 841, in _parse
p = _parse_sub(source, state, sub_verbose, nested + 1)
File "/usr/lib/python3.10/sre_parse.py", line 444, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
File "/usr/lib/python3.10/sre_parse.py", line 841, in _parse
p = _parse_sub(source, state, sub_verbose, nested + 1)
File "/usr/lib/python3.10/sre_parse.py", line 444, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
File "/usr/lib/python3.10/sre_parse.py", line 830, in _parse
raise source.error("unknown extension ?" + char,
re.error: unknown extension ?> at position 250
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "logparser.py", line 114, in <module>
File "logparser.py", line 101, in main
File "pipeline.py", line 163, in __init__
self._build_from_config(config)
File "pipeline.py", line 186, in _build_from_config
raise RuntimeError("Failed to construct %r step" % step_name) from ex
RuntimeError: Failed to construct 'audit-modsec-with-ts' step

Previously we had Ubuntu 18 with python 3.6, and the tool worked correctly.

any suggestions?

P.D.: Attached screenshot with the error, although in Spanish, sorry
 

Attachments

  • error_plesk_modsecurity.jpg
    error_plesk_modsecurity.jpg
    182.9 KB · Views: 5
What ruleset are you using for modsec?
In the tests we left the default Apache rules (Modsecurity 2.9), with the 'Comfortable' option and without custom directives.
We have also tried with some Nginx 3.0 rules, but always with the same error.

It's an unknown issue here, so probably contacting Plesk support at https://support.plesk.com will be best if it cannot be solved by community assistance.
Ok, I will wait a few days in case someone has the same problem and found a solution, otherwise I will write to support as you suggest, thank you very much
 
We have 3 Plesk installs that all have the same issue. All three were updated from Ubuntu 18 to 22.

I've been searching for a solution for about 2 months. This is the first report I've found that someone else is seeing this errror
 
Back
Top