As Dag Nabbit stated, a Minecraft server does not talk http. You would typically do this via NAT. A proxy server needs to know the protocol, because as the name suggests, it acts on behalf of the the client. Nginx knows various protocols, not just http, but Minecraft is not one of them. You can however write a proxy module for this protocol and use the existing nginx infrastructure. Since I'm not familiar with the protocol, I can't comment on the fact that this would have any advantages over NAT.
backup
...
Параметр нельзя использовать совместно с методами балансировки нагрузки hash, ip_hash и random.
/static/file.png будет искать файл /var/www/domains/example.com/static/static/file.png/static/file.png будет искать файл /static/file.png.server {
...
root /var/www/domains/example.com;
...
location /static/ {
}
location /media/ {
}
}/mediaholding/about пытается найти файл, а не спроксироваться в django. 
pageToken со значением, которое получили.messages = []
next_page_token = None
for _ in range(3):
if next_page_token:
msgs = service.users().messages().list(userId='me',maxResults=500, pageToken=next_page_token).execute()
else:
msgs = service.users().messages().list(userId='me',maxResults=500).execute()
messages.extend(msgs)
next_page_token = msgs['nextPageToken']
$ echo ${0}
/usr/bin/zsh
$ echo ${0##*/}
zsh
