I'm currently in the process of transitioning from wordpress to hugo.
For anyone not familiar with these, wordpress is php based and hugo
outputs static content (keeping it simple)
Currently wordpress is using ugly urls for posts, so "/?p=1234" in
wordpress might be "/this_nice_title" in hugo.
On Thu, Jan 30, 2020 at 04:46:27PM +, Johan Gabriel Medina Capois wrote:
Hi there,
> Here are two attached with required information, sorry for the time, anything
> else I'm available for send.
>
>From that, I do not see any evidence of a problem involving nginx.
You say that
On Thu, Jan 30, 2020 at 08:11:15AM -0500, MarcoI wrote:
Hi there,
> curl on PC-Server (Ubuntu 18.04.03 Server Edition):
>
> (base) marco@pc:~/vueMatters/testproject$ curl -Iki
> http://localhost:8080/
> HTTP/1.1 200 OK
So from the nginx-and-vue server, you can access vue.
> But from a
With this /etc/nginx/conf.d/default.conf :
server {
listen 443 ssl http2 default_server;
server_name ggc.world;
ssl_certificate /etc/ssl/certs/chained.pem;
ssl_certificate_key /etc/ssl/private/domain.key;
ssl_session_timeout 5m;
ssl_protocols
Thanks for the correction Maxim. I tested this before posting by using an
old certificate. Nginx did not throw an error but the browser did notify
that the connection was insecure.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,286852,286865#msg-286865
Sorry for my ignorance...
how to practically modify the /etc/nginx/conf.d/default.conf ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,286850,286864#msg-286864
___
nginx mailing list
nginx@nginx.org
GET https://localhost/sockjs-node/info?t=1580228998416
net::ERR_CONNECTION_REFUSED"
means it is connecting to localhost:443 ( default https port) and not port
8080
On Thu, Jan 30, 2020 at 6:41 PM MarcoI wrote:
> Hi Francis,
> thanks for helping.
>
> curl on PC-Server (Ubuntu 18.04.03 Server
Hi Francis,
thanks for helping.
curl on PC-Server (Ubuntu 18.04.03 Server Edition):
(base) marco@pc:~/vueMatters/testproject$ curl -Iki
http://localhost:8080/
HTTP/1.1 200 OK
X-Powered-By: Express
Accept-Ranges: bytes
Content-Type: text/html; charset=UTF-8
Content-Length: 774
ETag:
Hello!
On Wed, Jan 29, 2020 at 09:16:58PM -0500, slowgary wrote:
> Nginx does not validate the expiration date of certificates.
This statement is not true.
--
Maxim Dounin
http://mdounin.ru/
___
nginx mailing list
nginx@nginx.org
> I struggled with using the alias directive because I (incorrectly) assumed
> that it was relative to root since all other parts of my nginx configs are.
> This is not mentioned in the documentation, it'd be nice to see it there.
Well it's not directly worded but you can (should) see from the
10 matches
Mail list logo
