As stated in previous response, your bad gateway errors is directly related to DNS.
In the traceroute you provided can see it was done from a home network (mobilewifi.home)
With credentials provided me to your site, experienced NO errors.
Suggest this was really an issue with DNS on whatever machine you were using.
DNS is still messed up ...
The reverse lookups:
126.103.116.50.in-addr.arpa. 14400 IN PTR server.sorce.online.
126.103.116.50.in-addr.arpa. 14400 IN PTR server.kutaukufaku.com.
126.103.116.50.in-addr.arpa. 14400 IN PTR thedailyhoney.com.
still point to 3 domains.
Using Google's 8.8.8.8 dns resolver
server.kutaukufaku.com. 59 IN A 74.220.199.6
thedailyhoney.com. 3599 IN A 50.87.144.190
Neither of those IP's are on the same network ... and definetly NOT where your server is hosted - and definetly not the FQDN as provided by your own DNS server ns1.sorce.online whose records were changed just today:
sorce.online. 300 IN SOA ns1.sorce.online. root.server.sorce.online. 2018052100 3600 7200 1209600 300
The 2018052100 above is a date ... may 21.
Suggest you do this at home .... that wifihome network. edit your host file and make two entries like the following
50.116.103.126 learnit.sorce.online learnit
50.116.103.126 testlearnit.sorce.online testlearnit
Why do that? Every computer on the internet has to use DNS. Any computer, regardless of operating system will check the local computers host file for references *before* using DNS. With the above entries in your computer at home, there will be no more confusion as far as your workstation/home computer is concerned.
The mess with DNS, however, is something you'll have to get assistance with provider.
Even with ns1.sorce.online being the "authority' server for sorce.online, other DNS servers could come into play with other users ... ie, your students attempting to access your server.
DNS still resolves, in-correctly, the follwing:
;; ANSWER SECTION:
126.103.116.50.in-addr.arpa. 14400 IN PTR server.sorce.online.
126.103.116.50.in-addr.arpa. 14400 IN PTR server.kutaukufaku.com.
126.103.116.50.in-addr.arpa. 14400 IN PTR thedailyhoney.com.
Using Google's DNS resolver 8.8.8.8 this is shown for the second and third TLD's shown above:
server.kutaukufaku.com. 59 IN A 74.220.199.6 - is Bluehost ... OrgTechPhone: +1-888-401-4678
thedailyhoney.com. 3599 IN A 50.87.144.190 - is also Bluehost ... same number.
Bluehost needs to investigate why:
126.103.116.50.in-addr.arpa. 14400 IN PTR server.kutaukufaku.com.
126.103.116.50.in-addr.arpa. 14400 IN PTR thedailyhoney.com.
So all in all ... this is not a moodle issue - but a networking/DNS issue.
'spirit of sharing', Ken