No response from server about fsp-deployment-guide HOT 6 OPEN

Hey @pmesgari, first off thanks for buying the book! Sorry about that. Let's get you up and past this issue.

I'm confused on the server_name as fsa.techroomdeploy.site. That's not configured in Namecheap if the hostname is fsp. Also, what happens if you are on your server and perform a wget on localhost? Does nginx return anything? Or is nginx refusing to start?

from fsp-deployment-guide.

Hey @mattmakai thank you for the quick response.

I was just approaching the issue. So what I did is this:

• I deleted the record I added on Namecheap completely
• I run the ansible prod script again and this time I used the IP address of my Linode server directly in the all file for fqdn

In this way, the solution works fine! The page loads :)

But it appears it is the domain name that goes wrong. Could you give me a tip on how to configure the Advanced DNS record?

I attached two screenshots of my namecheap dashboard.

from fsp-deployment-guide.

Okay cool making progress... so you'll want your A Record for host www to be pointed to your server's IP address. Then set a URL Redirect record host @ record will be set to your https URL of your fully qualified domain. With those 2 records in place your Nginx configuration will handle the resolution for the domain name when it's properly configured. See example screenshot below for what you'd need:

from fsp-deployment-guide.

I don't know if that screenshot worked so trying again:

from fsp-deployment-guide.

Hi @mattmakai
So I went through the entire book on Saturday and Sunday, I must say one of the best books I have ever read in IT, thank you for that!

I still can't make the domain name to work. I set the records as you advised, and put the www.techroomdeploy.site as the fqdn value, but to no avail :(

Meanwhile, I faced a lot of problems with another part, the supervisor. The template files you have could not work for me, whatever I tried, and then I realized it was the supervisor package itself, it has a lot of problems with Ubuntu, also the version is quite old, so bugs haven't been resolved.

Instead, I created my own template file for supervisor that I share here with you. Having your feedback would be very much appreciated.

This is what I have for wsgi

###
# Sets up and configures Supervisor which runs Green Unicorn
##
- name: create Supervisor template for the WSGI app to run
  template: src=supervisor_app.conf.j2
            dest=/etc/supervisor/conf.d/{{ app_name }}.conf
  sudo: yes

- name: stop supervisor for app
  command: supervisorctl stop {{ app_name }}
  sudo: yes

- name: pause for restart to take effect
  pause: seconds=2

- name: start supervisor for app
  command: supervisorctl start {{ app_name }}
  sudo: yes
  notify:
    - restart nginx

And this is what I have for celery

###
# Sets up and configures Supervisor for Celery and Celerybeat
##
- name: create Supervisor template for Celery to run
  template: src=supervisor_celery.conf.j2
            dest=/etc/supervisor/conf.d/{{ app_name }}_celery.conf
  sudo: yes

- name: create Supervisor template for Celerybeat to run
  template: src=supervisor_celerybeat.conf.j2
            dest=/etc/supervisor/conf.d/{{ app_name }}_celerybeat.conf
  sudo: yes

- name: stop supervisor for celery
  command: supervisorctl stop celery
  sudo: yes

- name: stop supervisor for celerybeat
  command: supervisorctl stop celerybeat
  sudo: yes

- name: pause for restart to take effect
  pause: seconds=2

- name: start supervisor for celery
  command: supervisorctl start celery
  sudo: yes

- name: start supervisor for celerybeat
  command: supervisorctl start celerybeat
  sudo: yes

from fsp-deployment-guide.

hey @pmesgari, I need more information on "a lot of problems with supervisor". Are there specific errors in the logs?

from fsp-deployment-guide.