Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, try deactivating all plugins. If that resolves the problem, reactivate each one individually until you find the cause.
If that does not resolve the problem, try switching to the Twenty Twenty-One theme to rule out a theme-specific problem.
If that does not resolve the problem, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, ensure that you have set your SFTP or FTP client to view invisible files.
If you couldn’t resolve the problem by resetting your plugins and theme or renaming your .htaccess file, we might be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time. If you don’t have access to your server error log, ask your hosting provider to look for you.
Thread Starter
12sp
(@sp12)
Thanks. I will do all that stuff. 🙂 I’ll report back.
Thread Starter
12sp
(@sp12)
It wasn’t the plugins, themes, etc. I read that it might be a Twitter issue, so I posted on the Twitter community forums to see if they have any insight.
Did you also check the .htaccess file and find any error log entries for any errors that occurred during that specific time, as mentioned above?
Thread Starter
12sp
(@sp12)
Thank you so much for your help and suggestions. It wasn’t the .htaccess either.
I tried testing several pages/posts and it was a hit and miss thing. I never heard back from Twitter but I had read in a few different articles that if the validator gives that error, it’s usually on the Twitter side.
I waited, but that does seem to be what happen. The cards are working again, and the old tweets are showing the cards as well.
