I'm looking for help in recovering or accessing an old coursework website that I no longer have control over. The site is hosted under my ex's domain, and they're currently uncooperative about providing access to the files or fixing issues causing the site to buffer continually.
I've already tried using the Wayback Machine and Google Cache, but unfortunately, I couldn't recover anything through those methods. Given the circumstances, is there any way I can at least view the website or download the coursework from it? Eventually, I'd like to rebuild it on my own domain. Any suggestions or advice would be greatly appreciated!
4 Answers
Is your site a single-page application (SPA) or does it have directories? If it's just a frontend issue, you might be able to use Chrome DevTools to debug and potentially fix the code yourself.
Make sure you know whether it's an issue with just the domain or the hosting server itself. They’re not always the same; your ex could control the domain but have the site hosted elsewhere. If you can access the server, maybe you can move or repair the site there!
Thanks! I appreciate the clarification. I got a bit mixed up there, but it helps to know that they could be separate issues. I'll look into it!
This experience definitely emphasizes the importance of version control! Consider this a useful lesson for the future—using something like GitHub would really prevent situations like this.
It sounds like your ex is being difficult, which is frustrating. Since they control the domain, you might be stuck unless they choose to cooperate. The lack of information archived on the Wayback Machine means it wasn't saved, which is rough. At this point, you could try to remember or find any local backups of your work. This is definitely a lesson learned about not relying on someone else’s domain for important tasks!
Totally understood! I've learned my lesson the hard way. I guess I'll just work with what I do have and move forward. Thanks for your input!
I don't think it's a SPA, as I remember a directory structure. But I'll definitely give Chrome DevTools a shot! Another part of the site seems broken as well. Thanks for the tip!