sorry to bother you all . i can handle myself pretty good in some things , but in this particullar area , i am on junior level. I am successfully running a rocket.chat server with https access and i would like to assign to another instance(jellyfin server) also https . so in one vps to have two domains with https. But whatever i followed and i did , i am failing
4. Error messages and/or full log output:
if i try to add a 2nd domain with https , i end up without having https at all.
5. What I already tried:
basically i followed all instructions i have been given here:
whenever i am using the syntax Autotonic posted , both or either of my sites turned offline when i am trying to visit them from https . how can get the logs? , cause i tried a curl line and the output didnt seemed like logs.
and i am thinking also that when i run caddy version , it gives me the v2.1.1 , but the original install is from snap , do you think i might use the v1 ?
i am sorry but i am really newbie on those things , how can i provide you data(logs , etc) to post here
It’s unclear how you’re actually running Caddy. Is it running as a systemd service? If so, you should be able to get the logs by running journalctl -u caddy.
i am sorry for the messed up . i just dont have it.
the output in my terminal is
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
– Logs begin at Wed 2020-07-22 12:23:53 CEST, end at Sat 2020-07-25 07:24:04 CE
– No entries –
lines 1-2/2 (END)
Right on that page, it says how to check the logs with the installation they provide:
journalctl -r | grep caddy | less
It seems like it likely uses Caddy v1, not Caddy v2, but you might have a copy of Caddy v2 installed as well if caddy version gives you v2. I don’t know how you might’ve gotten that as well.
Their docs are entirely for Caddy v1. The versions are not compatible. Caddy v2 is a complete rewrite from ground up. proxy does not exist in Caddy v2, it’s a v1 directive. In v2, the equivalent is reverse_proxy and it has slightly different semantics. This is all covered in the upgrade guide:
So you’ll need to figure out what’s going on here.
ok i think i made a bit of a progress . i removed old version and installed v2 . i was able to replicate the successful use of my first domain . but i still cant assign https in my 2nd domain .
my config is :