error: sudo service nginx reload about microblog HOT 8 CLOSED

The microblog2 reference is a mistake, I'll correct that.

Does it work if you comment out the error_log and access_log lines?

from microblog.

thanks @miguelgrinberg for you answer. I have corrected the directory of microblog and commented out the error_log and access_log. After run the command: sudo service nginx reload, and there is no error. But accessed the application by the browser which input: http://192.168.33.10 , and there is error as following:

192.168.33.10 uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is not valid for the name 192.168.33.10. Error code: SEC_ERROR_UNKNOWN_ISSUER

In the Mac before this chapter, I just run: the flask run, and it can be accessed by: 127.0.0.1:5000.

from microblog.

This is not an error. The SSL certificate that you are using is self-signed, it is not going to be validated by the browser. From that chapter:

Because you are using a self-signed certificate, you will get a warning from the web browser, which you will have to dismiss.

from microblog.

hi @miguelgrinberg thanks for your answer. But I change a browser, the error is as following image.
Could you tell me how to run the app in server, after run the command: sudo service nginx reload.
I know in Mac, I just run:flask run, then go to browser to access it by 127.0.0.0.1:5000. How about in ubuntu server.

from microblog.

I don't use Safari that much, Does it give you an option to allow the invalid certificate? Most browsers do. If you have no choice to ignore the invalid certificate, then your options are to use a different browser (such as Chrome) or to add the certificate to the browser configuration, so that it is recognized as valid.

from microblog.

hi @miguelgrinberg thanks! After I changed to chrome, it works (I don't know why safari doesn't work), although, there is sign in error, I will fix it. By the way, if I want to deploy the app to AWS ubuntu. Are there some difference with vagrant?

from microblog.

Deploying to an EC2 should work in the same way as in your Vagrant VM. The only difference is in how you expose a public IP address to access the application to the outside, and also that you need to set up your security groups in the same way I set up the firewall.

from microblog.

This issue will be automatically closed due to being inactive for more than six months. Please reopen if you need more assistance.

from microblog.