Miscellaneous topics that do not fit into specific categories.
Hello Philip Levine,
Welcome to Microsoft Q&A!
Thank you for your post. I understand that you are having issue 500 Internal Server Error. I truly understand how you feel. Let me assist you further.
As your description, you're encountering a 500 Internal Server Error when trying to embed ICS calendar URLs from office365.com or live.com on a Liquid Web-hosted server. The same ICS links work fine on other servers, which suggests that Microsoft 365 is blocking your server's IP or domain from accessing calendar resources.
This is not email-related, so traditional email delisting steps may not apply directly—but there are still relevant actions you can take.
My suggestion for you to do further:
- Use Microsoft’s IP Delist Portal
Even though this is not email-related, Microsoft may still be blocking your server IP due to perceived abuse or misconfiguration. You can try submitting a delisting request here:
🔗 Microsoft Office 365 Anti-Spam IP Delist Portal
- Enter your server IP address and a valid email address.
- You’ll receive a verification email to confirm the request.
- This process is typically used for email, but it has helped in similar ICS-related cases
- Check Server Headers and ICS Request Behavior
Some users have reported that ICS links from Office365 redirect to error pages due to authentication issues or unsupported request headers
You can:
- Use
curlorInvoke-WebRequestto inspect the headers and response codes. - Compare working vs. non-working requests.
- Ensure your server is not sending headers that trigger Microsoft’s security filters (e.g., outdated user agents, missing auth tokens).
- Try Hosting ICS Proxy or Redirect
As a workaround, you could:
- Host a proxy script on a different server that fetches the ICS file and serves it to your Liquid Web server.
- This avoids direct requests from the blocked IP and may bypass the restriction.
- Additional Troubleshooting Tips
- Check for rate limiting or firewall rules on your server that might interfere with outbound requests.
- Verify DNS and reverse DNS records for your server IP—Microsoft sometimes blocks IPs with poor reputation or missing PTR records.
- Use a different IP or CDN temporarily to test if the issue is IP-specific.
I hope this helps in your situation. Feel free to let me know if you have another update.
Sincerely,
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment”.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.