Having difficulty downloading vanilla server.jar through AMP interface.

  • 154 Views
  • Last Post 22 April 2019
tuuatch posted this 22 April 2019

OS Name/Version:Ubuntu 18.04.2 LTS

Product Name/Version:AMP 1.7.4.4

Problem Description: While configuring a managed ADS instance for Minecraft server, I attempt to download the latest vanilla server.jar and the message "Download / Update failed : Couldn't determine the URL to fetch an update from. You may need to install this server type manually."

Steps to reproduce:

Step 1: Connect to instance.

Step 2: Select Configuration from the menu on the left. Select Minecraft from the menu on the left.

Step 3: In the upper right hand corner, select Official from the Server Type drop down menu.

Step 4: Click the Download/Update button.

Actions taken to resolve so far:

I reviewed the logs for clues. (

[10:15:23] [API:XXXXXX Activity]  : Updating the application.

[10:15:23] [Minecraft:XXXXXX Warning] : Couldn't determine URL to fetch update from.)

I have disabled and reenabled IPV6 on my server. I have attempted to download alternative versions (Spigot) which was successful. I have manually downloaded the server.jar and uploaded through the built in file manager. I was able to run the server after this but would like the ability to use the built in fetch and updater.

Thanks.

Order By: Standard | Newest | Votes
Mike posted this 22 April 2019

Restart the instance and give it a minute before managing it.

  • Liked by
  • tuuatch
tuuatch posted this 22 April 2019

I stopped the Minecraft instance and then restarted the ADS instance. I then restarted the Minecraft instance and waited over 20 minutes before attempting to manage it. I repeated steps used to reproduce and received the same resulting error. I have attached a snippet of the logs as well. Thanks.

[12:55:26] [WebServer Info]       : Webserver started on XXX.XXX.XXX.XXX:XXX

[13:08:55] [RemoteAMPAuth:Anonymous Activity] : Authentication attempt for user XXXXXX from XXX.XXX.XXX.XXX

[13:08:56] [RemoteAMPAuth:Anonymous Activity] : Authentication success

[13:09:06] [API:XXXXXX Activity]  : Updating the application.

[13:09:06] [Minecraft:XXXXXX Warning] : Couldn't determine URL to fetch update from.

Mike posted this 22 April 2019

Start it up with debug mode enabled and see if its having issues contacting the update server.

You can do this by setting Monitoring.LogLevel to 0 in AMPConfig.conf for that instance (stop the instance first)

  • Liked by
  • tuuatch
tuuatch posted this 22 April 2019

So the logging now shows this additional information:

[13:21:52] [WebServer Info]       : Websockets are enabled.

[13:21:52] [Minecraft Debug]      : Getting latest Minecraft server version information (async)

[13:21:52] [Minecraft Debug]      : Fetching info for Official

[13:21:52] [Minecraft Debug]      : Checking for installed plugins and retrieving metadata. (async)

[13:21:52] [Minecraft Debug]      : Web Error Fetching info for Official

[13:21:52] [Minecraft Debug]      : Error: NameResolutionFailure

but further down the line it also says this:

[13:21:52] [Minecraft Debug]      : Got info for Spigot OK

[13:21:52] [Minecraft Debug]      : Fetching info for Forge

[13:21:52] [Minecraft Debug]      : Got info for Forge OK

[13:21:52] [Minecraft Debug]      : Fetching info for Feed The Beast

[13:21:52] [Minecraft Info]       : Hash for server.jar: cf16dbe97dce13605d412811ea80c8b8

[13:21:52] [Minecraft Info]       : Using 'Official' compatibility mode.

So it appears to be connecting to the internet, which makes sense given some of the other versions did work when attempting to download/update Spigot, etc.

I forgot to mention in the original post that a troubleshooting step i took was to switch to the nightly branch. So I started out on 1.7.4.1 (I believe?) I do not have debug logs from that.

Mike posted this 22 April 2019

"NameResolutionFailure" - something is wrong with your internet access. It's trying to access launchermeta.mojang.com but can't resolve the hostname. Check your DNS settings.

tuuatch posted this 22 April 2019

I changed from my default DNS server (Pihole served locally) to the Google DNS servers at 8.8.8.8 and 8.8.4.4.

XXXXXX@ubuntu-new:/home/AMP$ ping -c 3 launchermeta.mojang.com

PING d1dulol58c5ch1.cloudfront.net (52.85.113.132) 56(84) bytes of data.

64 bytes from server-52-85-113-132.ind6.r.cloudfront.net (52.85.113.132): icmp_seq=1 ttl=244 time=16.3 ms

64 bytes from server-52-85-113-132.ind6.r.cloudfront.net (52.85.113.132): icmp_seq=2 ttl=244 time=16.5 ms

64 bytes from server-52-85-113-132.ind6.r.cloudfront.net (52.85.113.132): icmp_seq=3 ttl=244 time=16.8 ms

--- d1dulol58c5ch1.cloudfront.net ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2002ms

rtt min/avg/max/mdev = 16.305/16.574/16.878/0.235 ms

This does not appear to have resolved the issue. How could I download the other versions if I had an issue with name resolution? Wouldn't they all fail to resolve then?

Mike posted this 22 April 2019

What happens if you use ping6 instead of ping?

tuuatch posted this 22 April 2019

It fails but that is expected because launchermeta.mojang.com doesn't support IPV6. Seperately, I pinged google.com using ping6 and it worked fine.

Edit: I verified using this test site

Mike posted this 22 April 2019

Can you humour me and reboot the system?

tuuatch posted this 22 April 2019

Absolutely. I went ahead and rebooted. Crontab task restarted the ADS instance and I started the Minecraft instance. Same results unfortunately.

Edit: I went ahead and deleted the instance (Minecraft) and started a new one from scratch and that resulted in the same issue.

Close