Jump to content

VITAS

Members
  • Posts

    790
  • Joined

  • Last visited

Reputation

1,171 Excellent

Contact Methods

Profile Information

  • About me
    SpaceDock Admin
  • Location
    Behind the Mun
  • Interests
    you!

Recent Profile Visitors

9,874 profile views
  1. I do large scale KSP installations at Europes largest and the worlds second largest Hacker gathering every year. I use your chart as laminated printout for all those seasoned and new KSP players that use one of the many setups. I like the playfull and straight forward Design. Thank you for it.
  2. was at chaos comunication congress. I will update the site on 3rd jan. 16:00 CET The site will be down for 1h
  3. So that might coincide with me updating the reverse proxy. Thank you for the pointer. Small update: i havent found the cause yet. Im still on it. While you wait see it as retro. Vintage (DSL)modem speeds
  4. Hi, you are right its about 1Mbit/s up. Thats why to little for the bandwidth and load the setup has. I will look into this. Update: seems to be the reverse proxy. Im unsure as of know why it behaves that way. is the problem new?
  5. you might need to flush your cache. as i said shipf-click your reload button or refer to your browsers help on how to get the site loaded and not just displayed from cache. If youre still having problems please give me more details so i can debug it.
  6. The blank page problem is fixed. If its not for you try shift +click reload button. was quite a journey. the details are in my last posts. if you still have problems please tell me here. tech mumbo jumbo: i updated ates to 9.x. i had a temp problem with in between apache webserver throwing 400 errors. i had to fix it too and now it seems to do what it supposed to. i still need to iron out some stuff from mighrating all the old config entries to the new files and strucutres in ats. also 10.x got released so theres that as well as http/3 support to implement.
  7. Update on the FF132 issue: short version for non technical persons: its an avalance of work to get th^is going but i have an idea what to try. longer version for eggheads - the ats (apache traffic server) issue i opened after getting poitners form the mozilla issue told me to get an more up to date ats version. - im runnign ats 8.x now and need to jump at least to 9.x or even 10.x - ubuntu/debian are to oldschool to have these package versions. - fedora 41 server has 9.2 with 9.6 in rawhide (testing) and 10.0.2 in submission to testing but non of the needed extra plugins. (i would need to compile them on my own) - alpine linux has 9.2.5 in testing and all the plugins but im new to that distro and feel a bit uneasy using stuff from testing in critical prod envs. - in any case jumping by 1-2 major versions will have me redo all the folders ull of config files (thy switched from "strange" to yaml) - im not home till the end of the week and need to have at least a day of sitting down rewriting and debugging stuff to get this working. - i do thinking about compiling stuff on my own like in the olden days but id wish i could use package managers to keep things up to date. more advancements by mid next week is my guess im rooting for firefox and feel sad for not allowing its current version on my sites but it has to wait. any help with these issues: e.g finding rpm packets of the plugins for ats 9.2.5 or rpms for newer traffic servers would be great. you can also join the chat (link on spacedock) to pitch in.
  8. At least my site isnt the only one then. so my plan is to open an issue with apache traffic server refering to the mozilla one. i cant find anything that fixes my issue in the ats docs. i also need a way to deploy the latest ats version as lxc. i cant update to the latest ubuntu lts ver in the lxc on proxmox. it wont boot. so any idears in that department on how get a distro (any that has lxc templates in proxmox) to get ats 10 running?
  9. was on an event showing off ksp. i will investugate how i can implement a fix in apache traffic server sinc its the one that does the client https connection. if anyone wants to gi ahead and suggest ats settings to change/put in youre welcome. p.s. is this forum flake too? i had a hard time posting all threse webserver errors.
  10. i was unsure if the lookup does work. browsers have all sorts of things with dns they (can) do nowdays like dns over https. so the fact the os can lookup doesnt mean the browser can and is happy. the result is one ipv4 and one ipv6 because ipv6 has higher priority the network stack will auto use that if ipv6 is available and only fall back to v4 if not or connection fails. i will try to fix dnssec. its a good idear anyways. is there a way to get more debugging data than the error page we get? i can say that the problem exists for all my domains that use the apache traffic server rev proxy spacedock uses. so either it IS the domain setup (because i did it based on templates i made for all of them), the dns server or the rev proxy. In terms of versions for ATS (rev proxy) im a bit restricted because theres no distro i can run that has newer versions on offer as packets. but they are recent enough (at least they should). so bottom line: we dont have any clue what the issue is and thus how to solve it (yet)
  11. Yes ive added the needed DS RR in my domain providers panel but gotten an error from the info registry. ive opened a ticket on sundy with my domain provider but he hasnt gotten back to me yet i will cal him today. as you said i doubt this is suddenly a problem that should be taken so serious. but i think the "chain of trust" error of firefox gives us the clue that it might be it.
  12. i had a lot of problems with uptimes for the past month. ckan also does mirror mods whos lincense allow it to github. Apart form that its normaly that i dont change things but browsers add new restrictions that prevent the site from working there.
  13. What i know so far: i can reproduce the problem under Fedora 41 with FF 132. In general many pages have a delay in loading fromt ime to time so somethign with first contact or lookup is amiss. I indeed am missing the DS record in the TLD so the chain of trust IS broken. DNSEC sould be optional and a site laod shouldnt fail because of it not being supportetd by an NS. I added the missing entries for approval by the info registry but i got an error /delayed back. A Ticket with my domain registry is pending (its sunday). The mozilla changelog doesnt tell me what theyve changed that causes these problems. Someone could test this in other browsers like chrome. If they fail they might have better error messages. For now im waiting for word to get back from support. Workarround for now: dont use FF 132?
×
×
  • Create New...