Hi,
I'm a little confused about the relationship between conf files in
conf.d vs sites-enabled. Should server configurations be set up in one
directory or both? If either is there a "best practice" location? If
there are conf files in both locations which takes precedence? Some
sources I've r
Is this on a VPS? They might have and additional firewall on the hosting side
you need to adjust.
If this is behind a routwer and you are outside the network make sure to
port-forward port 443.
Sent from my Galaxy
Original message
From: Brian Carey
Date: 9/4/22 19:55 (G
Also just to give as much info as possible this is how I created the keys:
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout
/etc/nginx/ssl/biscotty.dev.ke
y -out /etc/nginx/ssl/biscotty.dev.crt
On 9/4/22 17:48, Moshe Katz wrote:
Here are a few things you can check (all of these nee
Thanks so much for your reply. See answers below.
On 9/4/22 17:48, Moshe Katz wrote:
Here are a few things you can check (all of these need to be run as
root or using `sudo`):
Is nginx actually listening on port 443? There are lots of different
commands you can use to check this, but I like t
Here are a few things you can check (all of these need to be run as root or
using `sudo`):
Is nginx actually listening on port 443? There are lots of different
commands you can use to check this, but I like to use `netstat -lptn | grep
nginx`.
Is there an error in your config? Check this with `ng
Hi,
I'm pretty new to nginx but do have a server up and running. I've been
pulling my hair out over ssl setup though. I have read the docs on your
server and some others like the alpine site. The most recent attempt I
followed the video tutorial on your website. Whenever I try to connect
via
You should verify that /run/nginx.pid actually exists and contains the PID
of the master nginx process on your Rocky Linux system.
I think that adding the "create 0640 nginx root" line to the logrotate
config file would not help. You can issue the "kill -USR1 " where you
replace "" with the PID o
Hi Vincent,
hope you're doing well.
On Sun, Sep 04, 2022 at 01:22:20PM +0200, Vincent M. wrote:
> Hello,
>
> The logs are working fine but once a day, nginx stop loging access and
> then the file log file is empty.
> So every day I have to restart my nginx server in order to get the logs.
> It'
On my Rocky Linux 9, I have found this file /etc/logrotate.d/nginx
/var/log/nginx/*log {
daily
rotate 10
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
/bin/kill -USR1 `cat /run/nginx.pid 2>/dev/null` 2>/dev/null ||
true
endscript
This sounds like your log rotation process is not signalling nginx to write
a new log. I don't know Rocky Linux, so I can't be specific in further
suggestions.
~ Frank
On Sun, Sep 4, 2022 at 7:24 AM Vincent M. wrote:
> Hello,
>
> The logs are working fine but once a day, nginx stop loging acc
Hello,
The logs are working fine but once a day, nginx stop loging access and
then the file log file is empty.
So every day I have to restart my nginx server in order to get the logs.
It's on a Rocky Linux 9 with Nginx 1.20.1
Never seen that before, what should I check?
Thanks,
Vincent.
___
11 matches
Mail list logo
