The migrator works both ways. You can use the link Marc provided to move your courses from GameDev.tv to Udemy.
@Marc_Carlyon may not know this if he has never needed to use that functionality before, but I’ve done it eleven times and I posted a pic below to show you.
- Go to the Udemy message center and open a message to GameDev
- Drop in this code: e86d47273260570507a1
- Wait just a few minutes for an update
I’ve personally done it eleven times to keep my Udemy and GameDev accounts reconciled.
Yes, eleven. I counted.
NOTE: Someone else mentioned also, the course needs to be available on Udemy for this to work. A few of the courses are not on the Udemy platform.
The instructions are here:
https://www.gamedev.tv/p/udemy-migrator
Also, I’ve had no issues playing the videos from GameDev.tv in either browser. I usually use Chrome, but I just checked Firefox and it’s working fine, too. There’s nothing wrong with the GameDev.tv site, as far as the website itself is concerned.
Keep in mind that different countries will access the same website using different servers, so even if I say ‘Mine works fine in the USA’, that doesn’t mean your experience will be the same if you live somewhere else, like Australia, or Romania, or Poland for example.
Just to be sure, try to ping the website and see if the site is up and running. The IPv6 address for the server I visit is right there in the pic: 2606:4700:3030::ac43:aebb
You can use either of these commands in cmd or Terminal to test for yourself:
ping gamedev.tv
ping 2606:4700:3030::ac43:aebb
Don’t be surprised if you ping gamedev.tv and see a different IPv6 address, or even an IPv4 address for that matter. It could be very likely that you’ll ping a different server.
Seeing as how you can log in and get to pages within the site, it’s not likely to be on the first six layers of the OSI Model (Physical Layer, Data Link Layer, Network Layer, Transport Layer, Session Layer, Presentation Layer).
Someone above suggested checking your browser privacy settings. While that COULD be the case, I’m not ready to fully believe that to be the issue. Here is why I think that way:
The dead giveaway is the 422 error you mentioned.
The 422 error is an HTTP error, and HTTP/HTTPS are Layer 7 protocols so the real question might be, is this the first time you’ve experienced this issue? Have you been able to watch the videos before?
It could also be some sort of regional thing, like China blocking certain content or something weird like that if you’re in that part of the world. It could be a bandwidth issue, or maybe a server side QoS issue (Quality of Service involves reserving resources for heavier loads, such as VoIP and video playback).
It’s likely server-side, but it’s not the fault of the site itself. It could be related to the infrastructure maintenance that someone mentioned above. The servers in your region might have been undergoing some sort of maintenance. The traffic should have been redirected to a fully functional server, if that was the case, but things do happen.
It could be that the RAID that was housing this content had a failed drive and was in the process of being replaced and rebuilt, once again, depending on the infrastructure.
I’m certain it’s an Application Layer issue (because of the 422 the HTTP error), but that could still point to a different type of hardware issue in a data center, such as not being able to find content because a RAID drive failed.
It wouldn’t hurt to double check some settings in your Firefox browser settings as others have suggested. You’ve done some due diligence when you loaded up Chromium.
You could also try testing with a different computer if you have one available. If you get the same issue on a different computer, then it’s going to point to the server side. If the videos play on the test computer, and not your regular computer then you might even try going as far as reloading your OS or doing a malware scan.
Side note: Hit me up if you want help reloading your OS. I can tell you how to get your product key if you’re using Windows, and make a bootable flash drive.
I wouldn’t rule out some form of DoS attack on your side, which could involve malware on your end that is preventing video playback. It might seem like a stretch, but it’s more common than you might think. An OS reload would most likely take care of that.
If a DoS attack was on the server side, it’s not likely that you’d get to the website at all.
Just above this post, someone posted about browser Privacy and Security settings. I would definintely check this first, as it could definitely cause something resembling a 422 HTTP error on Layer 7.
I hope this helps.