Step 7 of setting up the server on Ubuntu 18.04 doesn't work

[ShadyDemoness]

Hi there,

I followed your documentation of setting up the server on Ubuntu to the latter, but I struggle with the final step. Here's me running the the last command.

Then I tried this to solve it:

Obviously that also didn't work.

I'm stumped here. What can I do?

[AzDj]

You should use go run . But the error message should indicate that there is a problem with your environment Settings and that [gopath] is not configured correctly . Perhaps you can refer to this article for configuration or re-install Golang using a package management tool .

[Stefan240]

It is important to use sudo go run . (sudo is needed in this case to be able to bind the port that is used by the server, I will look into creating a systemd-service at a later date.) and the dot at the end is vital it tells what should be run.

Go worked fine for me while testing on ubuntu desktop, which is just ubuntu with GUI. I know the steps listed should work. If anything else arises please let me know.

[ricochhet]

It's always a good idea to follow exactly how the documentation shows it.

[ShadyDemoness]

......

Go seems to be installed correctly

[ShadyDemoness]

I followed the instructions completely. The first screenshot was from me replicating the issue and forgetting the fullstop

[Stefan240]

......

Go seems to be installed correctly

You did save Erupe to ~/Desktop/MHFZ Server/Erupe-master if I am not mistaken? Atleast thats what I see in your first screenshot. The command has to be run from where the files of the server are placed so your config.json, main.go, etc, etc please run the command from where the server actually resides

[ShadyDemoness]

I tried eliminating any error on my part and to make the file structure cleaner.

That's the reason erupe master isn't in there anymore

[Stefan240]

So I just tried running going through my instructions again, they work on Ubuntu 20.04. no problem. One thing I did notice is that your go-version is older than mine. I don't think this is the culprit but anyway. I had go1.13 running on ubuntu you have 1.10. Maybe your version is just too old?

Or something got funky. I would really just advice you to check again if you misread something or did not follow the instructions given. Which version of ubuntu are you running?

[ShadyDemoness]

I have Ubuntu 18.4 running on my rented root server.

Looked over every instruction again and nothing seems to be different.

Maybe it's really the Ubuntu version, which would suck.

[Stefan240]

Alrighty. I got down to the problem. Ubuntu 18.04 ships with an to old version of golang. So I could recreate your problem and solve it as well. Installing 18.04 it ships with go 1.10 which does not seem to work with this server. So the only thing to get it running is update go to something more recent by adding a PPA:

This Guide tells you how to do: https://computingforgeeks.com/how-to-install-latest-go-on-centos-ubuntu/ just use method 1 and install a more recent version of golang. Then all should work from here.

I will add this to the documentation at a later date, so I will keep this open for future reference till it is updated. Please report if this worked for you

[ShadyDemoness]

Ah thank you very much its working now. Though I would like to add something.

For people like me who have their own rented or bought root server, using localhost instead of the servers own IP seems to be the only thing working. Tried using the dedicated IP address but it spat out a port error which I would attribute to the nature of a root server.

I'll now install the client files on my home pc. Hope everything works out.

[Stefan240]

Ah thank you very much its working now. Though I would like to add something.

For people like me who have their own rented or bought root server, using localhost instead of the servers own IP seems to be the only thing working. Tried using the dedicated IP address but it spat out a port error which I would attribute to the nature of a root server.

I'll now install the client files on my home pc. Hope everything works out.

I tested the server on a VPS as well. It should work as long as you know the public ip of the server and have some port you can bind (80 is ideal but other ports can be used if say a webserver also resides on the server and 80 is already in use)

I might need to test around with that at a later date though.

[ShadyDemoness]

I'll get back to you after testing if using localhost on a dedicated server works out.

[ShadyDemoness]

Hi again,

using localhost didn't workout. I tried using the servers external IP in the config. My Root Server provider said they don't block any ports and because of that nothing requires port forwarding, I can attest to that as I didn't need to do port forwarding for any other hosting before. I also looked if I had set the firewall to enabled, which was not the case.

I tried migrating again but nothing changed. postgres seems to be installed correctly as well. Could this be an Ubuntu 18 issue again?

[Stefan240]

Hi again,

using localhost didn't workout. I tried using the servers external IP in the config. My Root Server provider said they don't block any ports and because of that nothing requires port forwarding, I can attest to that as I didn't need to do port forwarding for any other hosting before. I also looked if I had set the firewall to enabled, which was not the case.

I tried migrating again but nothing changed. postgres seems to be installed correctly as well. Could this be an Ubuntu 18 issue again?

Thats not related to Ubuntu 18.04 itself. two Things to check here. Make sure the postgres-database-server is actually started. If not start it. Make sure the password in the config.json matches the password of postgres. Also postgres is run locally only usually (on adresss 127.0.0.1)

[ShadyDemoness]

its working now. In the config I had to set the database IP to localhost and the Host Ip at the top to the external IP address of the server. The game crashed upon starting but I would guess that that's because of the HD resources.