A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Hi guys,
I have changed my URL for my wordpress website and now I cannot login any more. All solutions online recommend to access cpanel, however digitalocean doesn’t have this feature.
Could you please help me to reset my domain name on wp without using cpanel?
Thank you in advance! :)
do you have phpMyadmin installed? If not, that would be a good first start.
once you have that installed, you can log in to phpMyadmin and access the database for Wordpress. Find the table called “wp-options” and look for the site_url option. Make sure that matches what you want.
You might also scroll through and find the option named “front_page” and change that as well.
After you have made those changes, be sure to refresh your browser and try to log in to Wordpress (Hold down shift while reloading page..which will clear your cache and reload the page fresh)
I'm about to launch a major website. having a bit of a trouble with configuring SSL correctly, and need to make sure I don't screw it up. I do have SSL cert files, and following the guide here: https://www.digitalocean.com/community/tutorials/how-to-install-an-ssl-certificate-from-a-commercial-certificate-authority#install-certificate-on-web-server 1. I have an Nginx in front/root acting as a reverse proxy. 2. I have wordpress on Apache server at port 8090 3. and my app is at port 8000 (nodejs), consuming API from wordpress above. So my current setup is such: **1. /etc/nginx/sites-available/default:** ``` server { listen 80 default_server; listen [::]:80 default_server; root /var/www/html; index index.php index.js index.html index.htm index.nginx-debian.html; server_name domain.com www.domain.com; location / { proxy_pass http://localhost:8000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } location /wordpress { proxy_pass http://localhost:8090; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } } ``` **2. /etc/apache2/ports.conf:** ``` Listen 8090 <IfModule ssl_module> Listen 443 </IfModule> <IfModule mod_gnutls.c> Listen 443 </IfModule> ``` So, I suppose I need to modify ** /etc/nginx/sites-available/default:** like below. Just need someone to tell me if there's something wrong here: ``` server { listen 443 ssl default_server; listen [::]:443 ssl default_server; root /var/www/html; index index.php index.js index.html index.htm index.nginx-debian.html; server_name domain.com www.domain.com; ssl_certificate /ssl/domain.com.chained.crt; ssl_certificate_key /ssl/domain.com.key; location / { proxy_pass http://localhost:8000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } location /wordpress { proxy_pass http://localhost:8090; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } } ```
Nginx fails to call index.php file at '/' endpoint. In ```/etc/nginx/sites-available/default```, I have added ```location /``` section to rewrite to '/index.php' (see below). However, when I enter **my-site.com** to the url bar, I get 403 Forbidden error ([error] 18041#18041: *2 directory index of "/var/www/html/" is forbidden). When I enter **my-site.com/index.php**, it works correctly. Also, I'm able to see a page other than 403 Forbidden if I add an 'index.html' fie to my document directory, /var/www/html. Even with ```fastcgi_index index.php;``` and removed 'index.html', I don't see the index.php file in '/' endpoint. **/etc/nginx/sites-available/default** ``` server { listen 80; listen [::]:80; server_name my-site.com www.my-site.com; return 301 https://$server_name$request_url; } server { listen 443 ssl http2; listen [::]:443 ssl http2; include snippets/ssl-my-site.com.conf; include snippets/ssl-params.conf; root /var/www/html; index index.php index.html index.htm index.nginx-debian.html; server_name my-site.com www.my-site.com; location ~ [^/].php(/|$) { fastcgi_split_path_info ^(.+?.php)(/.*)$; if (!-f /var/www/html$fastcgi_script_name) { return 404; } include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME /var/www/html$fastcgi_script_name; fastcgi_pass unix:var/run/php/php7.0-fpm.sock; #fastcgi_pass 127.0.0.1:9000; fastcgi_read_timeout 300; } location ~ /.ht { deny all; } location ~ /.well-known { allow all; } location /phpmyadmin { index index.php; } # Rewrite rules for WordPress Multi-site. if (!-e $request_filename) { rewrite /wp-admin$ $scheme://$host$uri/ permanent; rewrite ^/[_0-9a-zA-Z-]+(/wp-.*) $1 last; rewrite ^/[_0-9a-zA-Z-]+(/.*\.php)$ $1 last; } } ```
I in the DNS records Control Panel records are shown in inverted creation order. A domain I'm managing is used by a Microservice architecture, there are many A records (Phisical Machines) and CNAME records (Services). It is becoming a bit confusing to manage it because when I need to add/edit/remove a service or machine it is not easy to identify the records involved in the process. Even worst some of my collaborators need to start editing the records themselves and it is not straight forward with this strange sorting. Would it be possible to reorder the records or maybe group them by type or both?
I have been researching for 3days but haven't find the solution for this email issue. I use Postfix to send out email on my droplet which is working fine for all email addresses but not for the email address that I assigned to the droplet. I have tried http://stackoverflow.com/questions/18377813/postfix-status-bounced-unknown-user-myuser and all other suggestions I found online but nothing worked. Here is my `etc/postfix/main.cf` ``` # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = goodnightjournal.com alias_maps = hash:/etc/aliases # virtual_alias_maps = hash:/etc/postfix/virtual alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = loopback-only inet_protocols = all ``` and I'm getting this error message on sending email to `o@goodnightjournal.com` from my contact form on the site. ``` Feb 23 01:30:41 goodnightjournal postfix/pickup[17494]: 492A4185557: uid=33 from=<www-data> Feb 23 01:30:41 goodnightjournal postfix/cleanup[17713]: 492A4185557: message-id=<d2b17d8f8fb99f252a50a823d0e8cbdb@goodnightjournal.com> Feb 23 01:30:41 goodnightjournal postfix/qmgr[17105]: 492A4185557: from=<www-data@104.236.98.136>, size=706, nrcpt=1 (queue active) Feb 23 01:30:41 goodnightjournal postfix/smtp[17715]: 492A4185557: to=<o@goodnightjournal.com>, relay=smtp.secureserver.net[68.178.213.203]:25, delay=0.48, delays=0.01/0/0.21/0.25, dsn=5.2.0, status=bounced (host smtp.secureserver.net[68.178.213.203] said: 550 5.2.0 <www-data@104.236.98.136> From: Domain is invalid. Please provide a valid From: IB506 <http://x.co/srbounce> (in reply to end of DATA command)) Feb 23 01:30:41 goodnightjournal postfix/cleanup[17713]: BEB9D185558: message-id=<20170223063041.BEB9D185558@goodnightjournal.com> Feb 23 01:30:41 goodnightjournal postfix/qmgr[17105]: BEB9D185558: from=<>, size=2817, nrcpt=1 (queue active) Feb 23 01:30:41 goodnightjournal postfix/bounce[17716]: 492A4185557: sender non-delivery notification: BEB9D185558 Feb 23 01:30:41 goodnightjournal postfix/qmgr[17105]: 492A4185557: removed Feb 23 01:30:41 goodnightjournal postfix/error[17718]: BEB9D185558: to=<www-data@104.236.98.136>, relay=none, delay=0.02, delays=0.01/0.01/0/0, dsn=5.1.3, status=bounced (bad address syntax) Feb 23 01:30:41 goodnightjournal postfix/qmgr[17105]: BEB9D185558: removed ```