Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

websocket issues #285

Closed
patricktresp opened this issue Jan 2, 2017 · 6 comments
Closed

websocket issues #285

patricktresp opened this issue Jan 2, 2017 · 6 comments
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@patricktresp
Copy link

patricktresp commented Jan 2, 2017

Hi all,
i just wanted to use this example for websocket:

https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/master/appengine/websockets

issue #1
usingvm: true in app.yaml is not supported anymore
issue #2
env: flex is missing in app.yaml
issue #3
forwarding posts is not allowed anymore in flex-environments
`network:
forwarded_ports:

  • 65080
    instance_tag: websocket`

issue #4
getExternalIP gets uncorrect ip-address from meta,
( scripts sets 104.xxx.xxx.xxx - console shows external ip as set to 130.xxx.xxx.xxx )
Does anyone have this example up and running on gce?

Main target is to create a websocket server which can be connected to from non gce-environmental clients...

thanks for help

@jmdobry
Copy link
Member

jmdobry commented Jan 3, 2017

The reason this example hasn't been updated to use env: flex is that env: flex does not yet support websockets.

@artpolikarpov
Copy link

artpolikarpov commented Jan 10, 2017

+1

@jmdobry
Copy link
Member

jmdobry commented Feb 8, 2017

There's nothing I can do for this until Google App Engine flexible environment supports websockets.

:/

@jmdobry jmdobry closed this as completed Feb 8, 2017
@shahbazahmed1269
Copy link

I am facing similar issue with port forwarding. I deployed a custom docker image of tcp server listening on port 6788 on app engine flexible environment. But seems like forwarded_ports: in app.yaml is not working.

Can we run a tcp server on app engine flexible environment? If so then how do I apply port forwarding from host port to container port?
Any help is appreciated.

@mcdaid01
Copy link

Is there any update on this issue, is it likely to be fixed in the near future?

@drBenway
Copy link

+1

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. triage me I really want to be triaged. labels Apr 6, 2020
NimJay pushed a commit that referenced this issue Nov 11, 2022
ace-n pushed a commit that referenced this issue Nov 11, 2022
ace-n pushed a commit that referenced this issue Nov 16, 2022
* updated CHANGELOG.md [ci skip]

* updated package.json [ci skip]

* updated samples/package.json [ci skip]
ace-n pushed a commit that referenced this issue Nov 17, 2022
* updated CHANGELOG.md [ci skip]

* updated package.json [ci skip]

* updated samples/package.json [ci skip]
ahrarmonsur pushed a commit that referenced this issue Nov 17, 2022
* updated CHANGELOG.md [ci skip]

* updated package.json [ci skip]

* updated samples/package.json [ci skip]
ahrarmonsur pushed a commit that referenced this issue Nov 18, 2022
🤖 I have created a release \*beep\* \*boop\*
---
## [3.9.0](https://www.github.com/googleapis/nodejs-secret-manager/compare/v3.8.1...v3.9.0) (2021-07-30)


### Features

* In Secret Manager, users can now use filter to customize the output of ListSecrets/ListSecretVersions calls ([#283](https://www.github.com/googleapis/nodejs-secret-manager/issues/283)) ([063691a](https://www.github.com/googleapis/nodejs-secret-manager/commit/063691a87291fab82037e9b444812dcf0724eb0c))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Development

No branches or pull requests

7 participants