#dynmap website wont load for select mobile browsers

1 messages · Page 1 of 1 (latest)

marble shale
#

last night my server was migrated to a different server and our IP was changed and since, select browsers (eg. safari on my iphone wont load it, but chrome will. or another members samsung wont load it on chrome) on both browsers we are getting the message

play.coronacraft.cc:8123 sent an invalid response```
valid ingotBOT
#

Thank you! Please provide any errors you are experiencing and upload your configuration.txt. Someone from our <@&801354402010628138> team will respond to help shortly. As a general reminder, everyone on our support team is a volunteer, please be kind!

toxic junco
#

the problem is your ssl certificate

#

I assume you used certbot to get the ssl certification?

#

force rerun certbot and see if it helps

#

if not then its time to go thorugh your external webserver config

raw reef
#

Is there an SSL certificate at all?

toxic junco
#

good question

#

if they only enabled force https without ssl certificate that would explain the question aswell

#

nvm

#

they didn'T enable force

#

I can access it via http

raw reef
#

I can access the map with safari on my iphone with no issues

marble shale
#

i’m gonna be real idk what an ssl certificate is

toxic junco
#

are you the server admin / dev?

marble shale
#

yeah i’m the admin

raw reef
#

I will take advantage of your issue to learn wether there is another way to do this, but I will tell you what I have in case it may help

#

The setup I find to be the cleanest and that I use is using Ngnix as a reverse proxy, this way I expose only port 443 and connections to my map don't include the ugly :8123 port.

Port 443 is the secure http port (which makes it https), and thus needs an ssl certificate to work, this certificate may be provided by your domain registrar; I use Cloudflare and I can generate certificates for my domain there.

Nginx is a web server, when put into reverse proxy mode, what it does is expose the port you like (443) and route all requests made to your dynmap's subdomain to the Dynmap application, which is hosted locally on port 8123

#

So if a user should search "play.coronacraft.cc", the request would enter port 443 to Nginx, which in turn would hand the request to Dynmap on port 8123 (you would specify this rule on Nginx, config)

toxic junco
#

(there is a very good step by step guide for this reverse proxy setup on the dynmap wiki)

#

I hope it is okay if I add some stuff

#

Optionally you could try to add a cloudfare ddoss protection in aswell, adding an additional layer of security.

toxic junco
marble shale
#

ok thank you guys i’ll look into this!

valid ingotBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.