How to add digitalocean nameservers to premiumdns in namecheap

I bought PremiumDns from namecheap 10 hours ago. I added 3 name servers of DigitalOcean to the customDNS but after I enabled the premiumDns, I can’t see the nameservers again. how to fix that, how to add the name servers to the PremiumDns?

The error is DNS error. The site is working now after I added digitaloceans nameservers to custom dns in namecheap.

ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com 

The problem There is no custom dns option in the premiumdns of namecheap, and they told me to find another way to add the nameservers.

I’ve contacted namecheap, they told me to contact digitalocean to find an alternative to the custom dns, but they don’t reply.

Can’t access my website with domain name with DigitalOcean

I’m using DigitalOcean for my hosting services and I’ve several domain names on the same droplets. All these domain use Let’s Encrypt for SSL certificates.


What’s your DNS records ?

|--------|---------------------------|--------------------------------------------|---------------| | Type   | Hostname                  | Value                                      | TTL (seconds) |  |--------|---------------------------|--------------------------------------------|---------------| | NS     | example.com               | ns1.digitalocean.com.                      | 1800          | | NS     | example.com               | ns2.digitalocean.com.                      | 1800          | | NS     | example.com               | ns3.digitalocean.com.                      | 1800          | | A      | example.com               | 159.xx.xx.60.                              | 3600          | | A      | www.example.com           | 159.xx.xx.60.                              | 3600          | | MX     | example.com               | mailstore1.secureserver.net.               | 14400         | | MX     | example.com               | smtp.secureserver.net.                     | 14400         | | CNAME  | 12501762.example.com      | sendgrid.net.                              | 43200         | | CNAME  | url9338.example.com       | sendgrid.net.                              | 43200         | | CNAME  | s2._domainkey.example.com | s2.domainkey.u12501762.wl015.sendgrid.net. | 43200         | | CNAME  | s1._domainkey.example.com | s1.domainkey.u12501762.wl015.sendgrid.net. | 43200         | | CNAME  | em8980.example.com        | u12501762.wl013.sendgrid.net.              | 43200         | |--------|---------------------------|--------------------------------------------|---------------| 
  • MX = allow the use of the GoDaddy mailbox (email like abc@example.com).

  • CNAME = allow the use of SendGrid.


So what’s my problem?

If I type in the browser:

  • example.com, I have a 404 error saying Apache/2.4.29 (Ubuntu) Server at example.com Port 80.

  • www.example.com, all is working and it redirects to the HTTPS version.

  • http://example.com, all is working and it redirects to the HTTPS version.

  • https://example.com, all is working.

So the problem is only with example.com.


Did you try ping function?

Yes. I ping with www.example.com and example.com and the both gave me the same IP address (my IP address).


What about traceroute ?

Again, it gave me the same for both www.example.com and example.com. It pointed to my server.


What about my .conf files?

Here the example.com.conf file:

<VirtualHost *:80>     ServerAdmin admin@example.com     ServerName example.com     ServerAlias www.example.com     DocumentRoot /var/www/example.com/public_html     ErrorLog $  {APACHE_LOG_DIR}/error.log     CustomLog $  {APACHE_LOG_DIR}/access.log combined RewriteEngine on RewriteCond %{SERVER_NAME} =www.example.com [OR] RewriteCond %{SERVER_NAME} =example.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> 

Here the example.com-le-ssl.conf file:

<IfModule mod_ssl.c> <VirtualHost *:443>         ServerAdmin admin@example.com         ServerName example.com         ServerAlias www.example.com         DocumentRoot /var/www/example.com/public_html         ErrorLog $  {APACHE_LOG_DIR}/error.log         CustomLog $  {APACHE_LOG_DIR}/access.log combined Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem </VirtualHost> </IfModule> 

Can anyone help me with this ?

Thanks for any help.

Install Windows in DigitalOcean Droplet for $5

I will install Windows Server on your VPS Digital Ocean Droplet we can do via Team viewer(better for your security) requirement Your Account Password Digital Ocean(you can change your password after work) I will install Windows server on your Digital Ocean DropletI will upgrade you Ubuntu Droplet into Windows and you can enjoy windowsAdditional Features: I will make the VPS/Droplet ready-to-use by: Jarvee Installing OpenOffice chrome firefox keepass 2 TeamViewer 14 RealVNC 7-Zip WinRAR

by: owravs
Created: —
Category: VPS
Viewed: 223


Problema com static files em deploy de projeto Django no DigitalOcean

Fiz deploy de um projeto Python e Django no Digitalocean, porém estou com problemas com static files

Dentro do meu projeto, na pasta static ao digitar o comando pwd para ver o caminho completo do arquivo, tenho o seguinte.

/root/getcode/notafiscal/getcode/static

Em settings.py eu tenho:

STATIC_URL = '/static/'  STATIC_ROOT = '/root/getcode/notafiscal/getcode/static/'  STATICFILES_DIRS = [     os.path.join(APP_ROOT, 'static'), ] 

e dentro de /etc/nginx/sites-available/getcode tenho o seguinte:

server {     listen 80;     server_name meu_endereco_ip;      location = /favicon.ico { access_log off; log_not_found off; }     location /static/ {         alias /root/getcode/notafiscal/getcode/static;     }      location / {         include proxy_params;         proxy_pass http://unix:/run/gunicorn.sock;     } } 

Porém, ao acessar o endereço IP, meu site está todo desconfigurado, como se não tivesse “lido” a pasta static.

Como resolver?

R script gets stuck on DigitalOcean

I posted the question on stackoverflow but maybe it is more appropriate here:

https://stackoverflow.com/questions/55409558/shelljs-execution-gets-stuck-on-digitalocean

Basically I have node application that is invoking R script. At some point it gets stuck and there are no errors. Looked into /var/log/syslog and see no out of memory errors. Looks as if something times out, but I would expect it being logged somewhere at least.

Unable to access resume device (/dev/volgroup00/logvol01) after CentOS custom image import DigitalOcean

I’m trying to import an existing CentOS VM from a VMware environment to run on Digitalocean vis their custom images option. I’m able to successfully run the VMDK in both VMware Workstation and VirtualBox. I’ve tried using the VMDK itself, and cloning the VMDK from VirtualBox to a VDI format, and uploading these to DigitalOcean and restoring. The restoration succeeds, but during boot, the below error occurs.:

root (hd0,0)  Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.18.164.11.1.e15 ro root=/dev/VolGroup00/LogVol00 rhgb quiet    [Linux-bzImage, setup=0x1e00, size=0x1d6b1c] initrd /initrd-2.6.18-164.11.1.e15.img    [Linux-initrd @ 0x37cab000, 0x344acb bytes]  Memory for crash kernel (0x0 to 0x0) notwithin permissible range WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong. PCI: PIIX3: Enabling Passive Release on 000:00:01.0 Red Hat nash version 5.1.19.6 starting   Reading all physical volumes.  This may take a while...   Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup/LogVol01) mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No suck file or directory setuproot: error mounting /sys: No suck file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempt to kill init!  Kernel alive kernel direct mapping tables up to 120000000 @ 10000-16000 

The only changes the VM went through between working on a desktop hypervisor and booting in DigitalOcean was the compressing of the VMDK/VDI file to gzip to make the upload more efficient. Would this be the cause, or is it more likely that the infrastructure differences between a desktop hypervisor and DigitalOcean’s infrastructure was enough to shake-up the volume names?

Any suggestions would be much appreciated.