Broken domains? Oy.

Open
#299 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
networking

Research direction

The report names feeder.scripting.com, xmlrpc.com, Digital Ocean, and HTTP but no project file or test. Start by reproducing both URLs and comparing their behavior across the reported server move; done means the cause is identified and HTTP access is reliably restored.

Written by the indexing model from the issue text.

Description

I have not been able to reliably get to a bunch of my sites that use HTTP this morning. For example, feeder.scripting.com, a site that I use to test feeds. Also xmlrpc.com. It's possible that something broke overnight in my server. Or Digital Ocean is having a problem? Doesn't seem like it's something Google is doing to punish me for using HTTP, though that is always the fist thing that comes to mind. I tried moving the XML-RPC site to a different server, but the problem follows it. No changes have been made to the site in years. Not exactly what I had planned to be digging into on a nice (but cold) Sunday morning in the mountains.

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.