where is my ics
Closed this issue · 23 comments
ive done it with the docker thing and put the conf in the .env if I go to my IP I get: couldnt get /. also I dont know where the ics file is so I cant add it to my calendar
First find your class ID in the /classes
endpoint, then use /timetables/<classId>
to retrieve the timetables for the given class.
Ok, thanks. How do I set up SSL it just says to put the cert.pem and key.pem files in a ssl folder but where/how do I get those files
And do I have to do SSL or is that optional
SSL support is discontinued, use a reverse proxy like caddy, caddy-docker-proxy or nginx to set up a reverse proxy.
This is what I get when I put it into the field in the calendar app on my ipad: IP:3000/timetables/825. I get the Error that "Validation failed"
This is what I get when I put it into the field in the calendar app on my ipad: IP:3000/timetables/825. I get the Error that the "Validation failed"
SSL support is discontinued, use a reverse proxy like caddy, caddy-docker-proxy or nginx to set up a reverse proxy.
Does it not work otherwise with the ical?
when I have my proxy running, do I just need to add the network in the docker-compose.yml of the ical sync?
I dont even get that message
I just get that the validation failed
This is what I get when I put it into the field in the calendar app on my ipad: IP:3000/timetables/825. I get the Error that the "Validation failed"
this is what I entered: IP:3000/timetables/825
Open that url in a browser and see if you get an ical output.
I cant specify the port 3000 in the calendar app
and otherwise it doesnt work
http://server.droplb.de/timetables/825 when I do that I get the insecure message but I dont get the ical output its useless
would it work id I changed the port to 80?
Sounds like some DNS issues on your end. The screenshot is indicating that it's clearly providing an ical output. Check your DNS records and/or port forwarding.
I use a local IP and tried with the public
but calendar says its invalid as soon as I specify the port 3000
Works now. Was just buggy