John Roberts
- JohnR
- JIRAUSER706554
- America/New_York
- Yes
- No
MC-241904
WEB-5513
Steps to reproduce:
- Download and run the vanilla Minecraft server software.
- Login and run /debug start.
- Wait for some time to pass and then run /debug stop.
Expected Result:
There should be a profiler result somewhere in the server folder.
Actual Result:
There is no profiler result found anywhere in the server folder.
When adding a user to my whitelist I receive a "That player does not exist" error. Here is a similar ticket,
WEB-4457, which explains how the curl request works.I am able to run the curl request on my residential network so it appears the server is not down. However, I asked my host to run the curl request on their node and it appears that Mojang's CDN, CloudFront, is blocking the connection. I asked them try it on a node in a different datacenter location, thinking I could just transfer my server, and they encountered the same issue. It would appear for that CloudFront is blocking datacenters from making the curl request necessary for whitelisting. This is problematic because many Minecraft servers are run in datacenters. I have attached a screenshot of the CloudFront error.
When adding a user to my whitelist I receive a "That player does not exist" error. Here is a similar ticket,
WEB-4457, which explains how the whitelisting curl request works.I am able to run the curl request on my residential network so it appears the server is not down. However, I asked my host to run the curl request on their node and it appears that Mojang's CDN, CloudFront, is blocking the connection. I asked them try it on a node in a different datacenter location, thinking I could just transfer my server, and they encountered the same issue. It would appear for that CloudFront is blocking datacenters from making the curl request necessary for whitelisting. This is problematic because many Minecraft servers are run in datacenters. I have attached a screenshot of the CloudFront error.
When adding a user to my whitelist I receive a "That player does not exist" error. Here is a similar ticket,
WEB-4457, which explains how the whitelisting curl request works.I am able to run the curl request on my residential network so it appears the server is not down. However, I asked my host to run the curl request on their node and it appears that Mojang's CDN, CloudFront, is blocking the connection. I asked
themtry it on a node in a different datacenter location, thinking I could just transfer my server, and they encountered the same issue. It would appear for that CloudFront is blocking datacenters from making the curl request necessary for whitelisting. This is problematic because many Minecraft servers are run in datacenters. I have attached a screenshot of the CloudFront error.When adding a user to my whitelist I receive a "That player does not exist" error. Here is a similar ticket,
WEB-4457, which explains how the whitelisting curl request works.I am able to run the curl request on my residential network so it appears the server is not down. However, I asked my host to run the curl request on their node and it appears that Mojang's CDN, CloudFront, is blocking the connection. I asked my host try it on a node in a different datacenter location, thinking I could just transfer my server, and they encountered the same issue. It would appear for that CloudFront is blocking datacenters from making the curl request necessary for whitelisting. This is problematic because many Minecraft servers are run in datacenters. I have attached a screenshot of the CloudFront error.
Short answer: I am connecting to https://api.mojang.com/profiles/minecraft using the /whitelist add command on my Minecraft server. I can not whitelist players who have not played on my server because when I do /whitelist add the connection gets blocked by CloudFront. This leads to a “That player does not exist.” error when whitelisting.
More information: Using the ticket that I referenced in the original post, I discovered that when you do /whitelist add the sever essentially is running “curl https://api.mojang.com/profiles/minecraft -X POST -H "Content-Type: application/json" --data '["Username"]'”. I asked the host to try this api request manually to diagnose why my /whitelist add command won’t work and it would appear that CloudFront blocks their datacenters.
My server’s requests comes from 23.158.176.176. (If my IP server’s can be removed or hidden from here after you are done with it that would be nice.)
I unfortunately don’t know which datacenters my host (bloom.host) uses. I know that many of their clients have the same issue. Perhaps I should advise my host to make a ticket here. However, I am only concerned about being able to whitelist on my own server. I thank you in advance and appreciate your help! I am pleasantly surprised by the level of support Mojang is providing here.