Categories
Uncategorized

How to fix the Warzone 2.0 game_ship.exe Error

game_ship.exe game_steam_ship.exe error

Summary

If you don’t feel like reading the whole post, here is the TLDR for you. Try enabling or disabling XMP, DOCP or EOCP depending on it’s current setting. For more information or context I suggest you read the rest of the post.

Introduction

If you’ve been playing or rather trying to play Warzone 2.0 (and you’re reading this post) there is a big chance that you’ve encountered the Game_Ship.exe error and it’s preventing you from finishing or even starting a game. After building a new PC for a friend 2 weeks ago, he’d been experiencing the same issue. I searched the internet far and wide but I could not find the solution, this was driving me insane. Did I make a mistake? Was it all my fault? Should he have bought a console instead? NO, NOT A CONSOLE, I won’t let this happen, I had to find a fix.

Generic Solutions

After hours of searching the only thing I could find were the most generic, click bait blog post articles I could find. You know what I mean:

  • Restart your computer
  • Verify the game files
  • Update your drivers (insert link to shady driver installer here)
  • Run the game as an administrator
  • Run the game in compatibility mode
  • reinstall the game
  • reinstall your operating system

I’m not saying that these things can’t fix your issue but I seriously have my doubts since these are the same “solutions” that get thrown around for every single game error.

Finding the right track

I had to go deeper, to the most knowledgeable people on the entire internet, and when I couldn’t reach them I went to Reddit. Here I found either, the same regurgitated “solutions” or a whole list of people who had the same problem but with no actual solution in sight.
Until I stumbled upon this thread, where I happened to see one comment that brought me to the right track in order to actually fix this problem.

shout-out to u\Ghostconn for posting his experience and guiding people to a potential solution.

This comment intrigued me since it at least made some sense, compared to some other “solutions” I read online. XMP, DOCP or EOCP are known to potentially cause some instability on your system. This instability might explain the game crashes. If you want to learn more about XMP and RAM overlocking I suggest you go read this post first.

Fixing the issue

I went into the BIOS to the RAM overclocking section and to my surprise I see the RAM set to 4800mhz, not 6000mhz like I was expecting. I guess I forgot to enable the XMP profile, or maybe the BIOS update changed it back? Okay… so XMP is already disabled… What now? With my back against the wall and my friend asking: “What if we enabled it?” I said fuck it, I turned on XMP and picked the advertised 6000mhz profile for his ram. Double check the BIOS settings on exit and fingers crossed… It worked… the game actually runs for the first time… We’re now 1 week further and haven’t had a single game_ship.exe error since.

Additional Suggestions

I can’t guarantee that this method will work for you as well but in case it didn’t, I do have a few extra suggestions.

  • Try reseating your RAM. RAM instability shows itself in weird and often unpredictable ways so if you experience other instabilities I would suggest trying this first.
  • After reseating your RAM test to see if everything is stable with Memtest86
  • In case you do run into further instabilities check for a BIOS update from your motherboard vendor. These often include stability fixes for higher RAM speeds, especially for the AMD side of things.

Conclusion

If these steps didn’t help you feel free to leave a comment with all your troubleshooting steps and their results below. Maybe I or others can find something and resolve the issue after all. In the meantime I guess you can try to contact Activision support but I wish you good luck with that.

Categories
Uncategorized

Setup a reverse proxy for your Homelab with Nginx-Proxy-Manager

What is a reverse proxy

In short, a reverse proxy is a webserver that is placed in front of other webservers and then forwards traffic to the requested webserver. The webserver then replies to the reverse proxy with the requested content which in turn forwards it to the client. With this setup a client is never directly connected to the content serving webserver.

Why use a reverse proxy

There are many reasons to implement a reverse proxy, the main reasons are security, performance and simplicity. In this post I’m mainly focusing on the security and simplicity aspects.

Security: I don’t want clients to directly connect to multiple machines in my network. I want as few servers/services accessible from the internet as possible.

Simplicity: unless you have multiple public IP’s (not really a thing for most homelabs) you can only expose ports 80 and 443 to one service. If you want to expose multiple services you would need to expose different ports and manually define them for each service. This is a pain to type or remember, and a reverse proxy solves this issue.

Install Nginx-Proxy-Manager with docker

Since this is a pretty bare bones docker install I’ll forward you to the installation page of the Nginx-Proxy-Manager project. Just make sure to note the ports that you set to talk to the container, by default these are 80, 81 and 443. 80 and 443 are used for the Reverse Proxy, while 81 is used to talk to the admin web interface.

Configure Port Forwarding on your router/firewall

Login to your router/firewall and forward port 80 and 443 to the ports that you picked for the container. For example if you changed 80 to 8080 make sure to forward port 80 from your firewall to port 8080 on the host that is running nginx-proxy manager.

Setting up the first reverse proxy

Open your browser to the nginx-proxy manager on port 81 (http://hostname:81).
Fill in the user information and change the password to something strong and secure.
Go to proxy hosts and select “Add Proxy Host”

The domain name would be how you want to access the site from the outside for instance test.roadtosysadmin.com. The scheme is for the internal website, if your webserver internally only serves http, pick http. Fill in the Hostname or IP form the webserver and the port that it answers to.

You can save these settings for now.

Pointing the domain name to your public IP

If you haven’t configured your (sub)domain go to your registrar or DNS provider and create and A record or CNAME that points to your public IP. Since every registrar is a bit different you’ll have to google this yourself if you’re not familiar with this. If you don’t have a static IP address (like many residential users) you can use a Dynamic DNS service (DDNS) like DuckDNS. If your A or CNAME record is created and points to your public IP/DDNS service, see if you can access your webpage in http, since we haven’t setup https yet. Note that it might take a couple hours for the changes to take effect.

Configure HTTPS/SSL

Go to SSL Certificates and click on “Add SSL Certificate”

Since Let’s Encrypt certs are free we’ll pick this one.
Type the domain or subdomain that you configured earlier. If you plan on using multiple subdomains in the future you can also use *.mydomain.com, this way you only need to renew one cert for all subdomains. Fill in the email you want to be notified on in case of renewal issues.
Agree to the terms and click on save.

If your certificate is configured you should now see and expiration date. Let’s Encrypt certs are only valid for 90 days, but the certbot will try to renew them after 30 days so it has plenty of time to retry in case of an issue. You will receive and email if the cert hasn’t been renewed 1 week before expiration.

Go back to the proxy host that you created earlier, click on the 3 dots on the side and pick “Edit”. Now go to the SSL tab and select the certificate from the drop down list. I recommend you also select the Force SSL switch while you’re in there.

Now browse to your site in https and see if everything is working as intended.

Additional security with Cloudflare Proxy

To add some extra security to your setup you can also use a Cloudflare proxy in front of your own reverse proxy. If you’re interested in this defiantly check out my next post.

Categories
Uncategorized

How to setup Enterprise Mode Site List with GPO

In this tutorial I’ll explain what Enterprise Mode Site List for Edge (Chromium) is, why you should use it and how to enable it.

What is Enterpise Mode Site List for Edge?

Enterprise Mode is a feature build into the “new” Microsoft Edge Chromium that allows you to specify certain websites to render with the old Internet Explorer engine. It still looks like the site is opened in Edge but in the background it’s actually being rendered by IE.

Why should you use Enterpise Mode?

Everybody probably has this one internal site that still requires IE to function. You know the one, built in 1995 buy one guy that left the company 10 years ago. So to make the life of end users and yourself easier, you can use Edge Enterprise Mode. This way you can force Edge to render that specific site with the IE engine. This means that from now on, all your end users can Edge as their one and only browser instead of juggling between IE end Edge or even worse only using IE.

How to setup Enterprise Mode.

First of all make sure everybody is on the latest build of the Chromium based Edge, this will not work for the older Edge.

Creating the list

There are multiple ways of creating the XML that specifies which sites that need to run under IE. The easiest would be using the Enterprise Mode Site List Manager which you can download here

  • Open the Enterprise Mode Site List Manager
  • Click add
  • Enter the URL of your website (I’ll be using google.com for this)
  • Select Open in IE11
  • Select the Specific IE version you need for the Compat Mode, this will of course differ from site to site.
  • When all your sites are added go to file and save to XML
  • Save this XML file to a location that everyone in your company has read rights to

Site list versions

In the Enterpise Mode site list you can see a version number on the right hand side. This number is important as Edge needs to check that number before it accepts the changes. This means that for every change you make that number needs to go up, otherwise Edge will not look at the changes. This works automatically when you use the Enterpise Mode Site List Manager, but you need to think of this when changing the xml file manually.

Setting up the Group Policy

  • Install the Group Policy files you can find these here
  • Create a new Group Policy
  • Go to Computer Configuration -> Policies -> Administrative Templates -> Microsoft Edge
  • Enable the ‘’Configure Internet Explorer Integration” Policy
  • Enable the “Configure the Enterprise Mode Site List” Policy
  • Place the path to the XML file in the options box

Testing the config

In order to see if Edge configuration is working, simply open Edge and go to the specified site. If everything is working as it should you should see a little Internet Explorer icon to the left of the URL.

If things are not working as expected you can go to edge://compat/enterprise. Here you can see if the policy is applied and if Edge is using the right version of the XML file.