Enable HTTP/2

[elf-pavlik]

It seems that solidcommunity.net doesn't have HTTP/2 enabled. It should be easy to enable it no matter which reverse proxy is being used.

I don't see any reason not to use HTTP/2, and in case of Streaming HTTP notifications having it disabled will lead to reaching browser's limits on connections to one domain.

[bourgeoa]

Thanks for raising the issue.

Nginx is used.
http2 has been enabled on the test server https://pivot-test.solidproject.org on all open ports 443, 8443, 3000 and 3100

This is the new nginx configuration
inspired from https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-with-http-2-support-on-ubuntu-22-04

root@solidtest:~# nano /etc/nginx/sites-available/http_to_https

# redirect all http to https
server {
    listen 80 default_server;
    listen [::]:80 default_server;
    server_name _;
    return 301 https://$host$request_uri;
    listen 443 default_server;
    listen [::]:443 default_server;
    listen 8443 default_server;
    listen [::]:8443 default_server;
    listen 3000 default_server;
    listen [::]:3000 default_server;
    listen 3100 default_server;
    listen [::]:3100 default_server;

    http2 on;
    ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
}

root@solidtest:~# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
root@solidtest:~# systemctl reload nginx.service

[bourgeoa]

Shall wait for ODI to update solidcommunity.net

[ewingson]

this seemed to be a good fit for my question, although its not strictly maintenance of sc.net 👍

http2 enabled on solidweb.me

$ curl -i https://solidweb.me
#HTTP/2 301 

however, the Pivot on teamid.live is running on port 443 without nginx, so trying to enable nginx gives me
address already in use.

the pivot starts with

npx community-solid-server -c ./config/prod.json ./custom-config.json -f /var/www/html --httpsKey /etc/letsencrypt/archive/teamid.live/privkey1.pem --httpsCert /etc/letsencrypt/archive/teamid.live/fullchain1.pem -p 443 -b https://teamid.live/ -m .

any ideas for a way out ?

[elf-pavlik]

You should be able to remove --httpsKey and --httpsCert and start it on some other port which you would use in nginx config.
Can't you just reproduce your deployment from solidweb.me on teamid.live and only use different CSS configs?

[ewingson]

have moved the discussion to serverproject-dev/teamid.live#1