# Security issue on initial access to Gramps installation hosted by Digital Ocean **URL:** \ **Category:** Gramps Web\ **Created:** [January 16, 2024, 4:48pm UTC](https://gramps.discourse.group/t/security-issue-on-initial-access-to-gramps-installation-hosted-by-digital-ocean/4692 "2024-01-16T16:48:12Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![geophile](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/geophile/32/3799_2.png) [@geophile](https://gramps.discourse.group/u/geophile)\ **Post date:** [January 16, 2024, 4:48pm UTC](https://gramps.discourse.group/t/security-issue-on-initial-access-to-gramps-installation-hosted-by-digital-ocean/4692/1 "2024-01-16T16:48:12Z")
[If I’m asking this in the wrong place, please accept my apologies and redirect me.] I am brand new to GrampsWeb, and followed the directions for deploying on Digital Ocean. I created a domain on DuckDNS, let’s call it [newbie.duckdns.org](http://newbie.duckdns.org). I ssh’ed to my “droplet”, entered the DNS name, and installation seemed to proceed normally. I then, from my browser (firefox on PopOS, an ubuntu variant), entered [https://newbie.duckdns.org](https://newbie.duckdns.org), and saw: Warning: Potential Security Risk Ahead … A similar problem occurred using the Brave browser. Has anyone else encountered this? ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [January 16, 2024, 6:20pm UTC](https://gramps.discourse.group/t/security-issue-on-initial-access-to-gramps-installation-hosted-by-digital-ocean/4692/2 "2024-01-16T18:20:34Z")
Double check your DNS set-up or check the docker logs. Either you didn’t set it up correctly or obtaining a certificate failed for some reason.