Skip to content

jadurani/360degrees-company-website

Repository files navigation

360degreessystemscorporation.com

Revamped Website Preview

Author

Designed and Developed with ❤️ by Jadurani Davalos ([email protected])

Systems & Subscriptions

Pre-existing and Paid

New and Still on the Free Tier

These are accounts and services introduced by @jadurani when she built the new 360degrees website

How to add a new project

Reach out to [email protected] to request the video recording of adding / updating projects and images

Issues encountered

The following were encountered during web support and development.

1 - Cannot deploy to 360degrees.com.ph

IP Addresses were misconfigured.

Protocol Domain IP Address (when pinged) Remarks
http://360degrees.com.ph/ 185.230.62.177
http http://360degrees.com.ph/ 45.79.222.138 Questionable. ping http://360degrees.com.ph should not have worked
https https://360degrees.com.ph/ 45.79.222.138 Questionable. ping http://360degrees.com.ph should not have worked
http://cpanel.360degrees.com.ph/ 182.18.209.197 The website I’m testing to deploy via cpanel gets deployed in 182.18.209.197 instead of http://360degrees.com.ph/
http http://cpanel.360degrees.com.ph/ N/A
https http://cpanel.360degrees.com.ph/ N/A
http://360degreessystemscorporation.com/ 185.230.63.171
http http://360degreessystemscorporation.com/ N/A
https http://360degreessystemscorporation.com/ N/A

Upon contacting the dotPH support team, they've confirmed that there were issues with how the domain records were set in the nameserver.

The nameserver being used right now are the following:

  • ns1.skybb.ph
  • ns2.skybb.ph

The dotPH team confirmed that these are not the default nameservers provided by dotPH, a critical info that changes my opinion on the matter. This means that even if we transfer the domain ownership, we will still have the same problems and if we want to fix the issues about the records, we will need to access the current nameserver (skybb).

In order to proceed with the full transfer of control (and not just domain ownership), we'll need to move away from the current nameservers--away from *.skybb.ph--and either use another external party or use the default nameserver provided by dot.ph.

Upon contacting the Atlantis team, they also said that they only have access to the domain itself and that they have no access to the nameservers.

The impact of the transfer can be drastic and we need to be extra careful in managing the risks--we need to back-up all data, especially the emails.

2 - Limited Deployment Facility in cPanel

The current cpanel plan has limited functionalities in deploying a custom website, e.g. a Node.js application.

Further Discussion

  • When or how the nameservers were changed could no longer be tracked and there were no leads on who did so.
  • The option of having a self-owned domain, website hosting, and email hosting carried far more risks and costs than retaining the current set-up. This option would also require having to back-up all the emails that are currently hosted in the shared cPanel subscription and having some downtime in the services.

Decision