chrome speculation rule gives server 500 error, but cannot find it

hub2000

• December 19, 2024 09:43

Hello,

we want to use the chrome speculation rules. Unfortunately, it gives a server 500 error.

To see more information we looked into server logs, but cannot find the entry and no more information at following location:

/var/log/apache2
/var/log/apache2/domlogs
/var/log/apache2/domlogs/user

So my question is:
- where is the server 500 error stored
- how to get more information about this error?

Hubertus

 

 

 

 

 

 

• 

  cPRex Jurassic Moderator

  • December 19, 2024 14:14

  Hey there!  500 errors would get stored in the main Apache log, which is located at /etc/apache/logs/error_log on the system.  Can you check there and see if there is anything helpful?

  0
• 

  hub2000

  • December 19, 2024 18:27
  • Edited

  Hello,

  thank you for your support. This folder is not available, its symlinked to:

  /var/log/apache2/error_log

  And this log does not show this error. After deleting the file it remains empty after generating the 500 server error.

  0
• 

  cPRex Jurassic Moderator

  • December 19, 2024 19:10

  Thanks for the additional details.  I'm honestly not sure what else could be causing this as the output from the screenshot shows a 500 error from Apache, so I would expect that to be logged on the server in the main Apache log.

  Do you at least see the access attempt in /etc/apache2/logs/access_log to confirm the request is reaching your server properly?

  0
• 

  hub2000

  • December 19, 2024 19:42
  • Edited

  Hello,

  no, in
  /var/log/apache2/access_log

  i do not see these attempts, but in ...ssl.log:

  "IP of my server" - - [19/Dec/2024:20:35:33 +0100] "HEAD /mobelfolie.html HTTP/1.1" 500 - "-" "curl/7.29.0

  0
• 

  cPRex Jurassic Moderator

  • December 19, 2024 20:26

  I don't have a good explanation for this behavior, especially if it's not reaching the Apache access log. 

  0
• 

  hub2000

  • December 20, 2024 10:57
  • Edited

  But, the 500 error is reaching the log according the log line.

  Or do we miss more specific information in this line?

  LogLevel is actually "warn", but its the same bevaviour with level "debug": no more specific information.

  On the other hand: what is specifically needed as a apache module in order the speculationrules are working?

  0
• 

  cPRex Jurassic Moderator

  • December 20, 2024 20:19

  Since these aren't rules that cPanel provides, I can't say what may be needed to get this working.  If you'd like to submit a ticket we could possible do more digging, but the issue doesn't seem to be related to cPanel or any of its configurations.

  0

Please sign in to leave a comment.