#CORS Issue
26 messages · Page 1 of 1 (latest)
I can confirm runpod is not the issue
KoboldAI also heavily relies on cors
If cors fails my UI tells me, and I have no issues with the KoboldCpp template
What I do see is that your runpod URL is 500
The other appears like a hacky version of Huggingface Chat
Thanks for nothing?
Get a clue, life, anything?
Your 100% on your own now
And your an asshole and don't need your help.
No, you are the asshole and insulted me for helping
hacky huggingface chat ... def not a problem when the same docker runs elsewhere .. just go away moron
Am I wrong?
clap clap your so smart ... wtf dude .. do you know what a fork is ...
do you know what docker is ...
do you know anything apart from kiddy scripting for kobold?
Considering I built the dockers and mine work including cors, yes I know what docker is
ok so if code works on one host ... but not the other what is the difference?
Thats a fun question you would have possibly had an answer to had you not insulted me
ahuh because you started so politely ...
and you we're being friendly not an unhelpful asshole at all ... and it's MY fault ...
Where is your "HACKY" Kobold version i can piss all over?
If you can't see I told you what was wrong as to why cors is failing so you have an idea on how to fix it thats on you. Either way I have no reason to continue the conversation.
Fuck me ... yes its a 500 error caused by a CORS fault .... FFS. thanks for the trolling asshole I reported you.
You gave NOTHING of value .. skill or intelligence