from the client's perspective, receiving 500 messages/sec seems like a lot, especially if the client is an end user UI. I wonder if a human can perceive this resolution of data or if it could be collapsed into fewer messages?
collapsing into some interval frame size is a great idea, i'll try it now, should definitely help.
I'm using Let's encrypt with pushpin on port 4430, I've symlinked the certs to
/etc/pushpin/runner/certs/default_4430.key and /etc/pushpin/runner/certs/default_4430.crt from /etc/letsencrypt/live/domain.xyz/fullchain.pem and /etc/letsencrypt/live/domain.xyz/privkey.pem and confirmed they are available, but I get the error ERR_SSL_UNRECOGNIZED_NAME_ALERTor tlsv1 unrecognized name. Tried to find information about this, but none available for Condure. What to do?
I don't see any errors in either pushpin nor Condure logs.
@jdegger usually you'll get a mail within a few days
hi @jkarneges thx for the reply :-) i am a little rookie on pushpin. if i want to ratelimit websocket request trough kong api gateway, but kong cant register websocket request.
Can pushpin route the request to kong so it can see the requests? pushpin can convert/ ws to http?
And how will a route look like in pushpin ?
@SimonNi59475821_twitter do you already have a websocket server and you're wanting to ratelimit the requests to it? pushpin can convert websockets to http, in order to send to kong, but this won't help if kong needs to then send websocket connections to a websocket backend server
Hi, pushpin-newbie here ;) I'm trying to get a pushpin instance going. What I've got so far is a running EC2 Ubuntu instance on which I installed pushpin. I verified that the service is actually running. But when I try to connect to the client from my machine via the curl command stated in the getting started guide, it times out. I'm assuming it's because ports 80 and 443 aren't open on my instance (I checked with
lsof -i and they don't show up there). Is there any documentation on what the requirements of the server are that is running pushpin? I'm also quite new to the networking topic in general and so I'm just assuming that I need to install apache or some other kind of web server on the pushpin instance if I want to get the http/s traffic working. Please correct me if I'm wrong. I'll appreciate any input on this :)
for authbind, I think you'd need to install the authbind ubuntu package, and then create an empty file
/etc/authbind/byport/80 that the pushpin user has access to
you could also leave pushpin running on port 7999 and put a proxy in front of it. at our company, we use haproxy for load balancing in front of pushpin for example. but there is nothing wrong with running pushpin on standard ports and having clients connect directly to it
Hello, I created a working version of Arm64 Container. For those interested: https://hub.docker.com/r/zimbres/pushpin
@jkarneges: is there a release being planned that rolls in changes since the last release? I am also seeing some strange connection issues with websocket proxy in Ubuntu 22. Any one else face similar issues?
zurl log shows frame-to-large error message which causes the connection to be reset. Is there a setting to side step this in zurl? Or is this just a symptom.
That did not help, strangely things work fine in Ubuntu 20.04 but not on Ubuntu 22. I am trying to compile and use 1.35.0 release source
The backend does send large frames but I don't think they are 2MB large. I had set the buffer size to 2000000.
I wonder if there is a clue in why it works on Ubuntu 20 but not 22? Did some default change?
Both cases I built it from 1.35.0 source tar.gz
zurl/focal,now 1.11.0-1 amd64 [installed] on ubuntu 20.04.4
zurl/jammy,now 1.11.1-1 amd64 [installed] on ubuntu 22.04.1
condure/fanout-focal 1.7.0~focal1 amd64 [upgradable from: 1.6.0~focal1] Ubuntu 20
all I can think of is the flow control varies for some reason (maybe performance differences) and this ends up changing the frame sizes
try setting an even larger buffer_size in zurl? also check to make sure the setting is really getting used, i.e. the value got written to zurl.conf and
ps shows zurl using that conf file
Ok will try it out. Is it possible to have the websocket pass through proxy route traffic to two backends simultaneously and use one of the results?
The config format for fallback is not obvious to me from the docs. What I meant is for performance reasons the request can be sent to backend1 and backend2. Whichever arrives first can be used.
but they aren't used simultaneously as you describe
admittedly this is pretty limiting. probably better to just use a load balancer
Is pushpin smart enough to avoid sending the same request upstream when a preexisting upstream connection is requesting the same websocket method?