a year ago
Maybe it has something to do with new code?
34 Replies
a year ago
i would have to say blinko changed something in the last 3 months
a year ago
fair enough
a year ago
i'll see what happened
a year ago
yeah its broken, even the official template doesn't work
a year ago
time to open an issue
a year ago
what needed to be changed?
a year ago
tbh i've no idea, I just get a 502

a year ago

a year ago
maybe ipv6 stuff?
a year ago
not listening on 0.0.0.0 or the wrong port
a year ago
port is the right one
a year ago
so yeah probably not listening on 0.0.0.0
a year ago
a classic
a year ago
what framework is used
a year ago
nextjs as it seems
a year ago

a year ago
there's a variable to tell it to listen on a specific host
a year ago
I don't remember it off the top of my head
a year ago
uhhh

a year ago
i'll try that variable
a year ago
uhm i could not find that variable
a year ago
love the blame on our platform
a year ago
I think the variable you need is just HOSTNAME=0.0.0.0
a year ago
believe it or not it worked 💀
a year ago
sweet
a year ago
its always something simple
a year ago
i'll mention that on the issue
a year ago
or maybe you could add yourself? idk
a year ago
i think someone needs to improve their google foo 😉
a year ago
i really tried tho 😭

a year ago
too vauge

a year ago
PR open
https://github.com/blinko-space/blinko/pull/535
thread can be closed
a year ago
sounds good to me
a year ago
!s
Status changed to Solved brody • about 1 year ago