Replies: 1 comment
-
Your socket.io connection should use the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Everything works well and dandy during dev on localhost. On the server, however, I'm getting error:
Mixed Content: The page at '' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://url.com/socket.io/?EIO=3&transport=websocket'. This request has been blocked; this endpoint must be available over WSS.
Expected behavior
Tell us what should happen
Websocket connects and works.
Actual behavior
Getting error in browser's console about insecure socket
Mixed Content: The page at '' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://url.com/socket.io/?EIO=3&transport=websocket'. This request has been blocked; this endpoint must be available over WSS.
NodeJS version:
14.17.1
Operating System:
Ubuntu
Browser Version:
Chrome
Version 91.0.4472.114
My client config is as below:
import feathers from '@feathersjs/feathers'
import socketio from '@feathersjs/socketio-client'
import auth from '@feathersjs/authentication-client'
import io from 'socket.io-client'
//To store local cookies
import { CookieStorage } from 'cookie-storage'
//API URL
export const host = 'https://***.com'
const socket = io(host, {
transports: ['websocket']
})
const storage = new CookieStorage()
const feathersClient = feathers()
.configure(socketio(socket))
.configure(auth({ storage }))
export default feathersClient
Beta Was this translation helpful? Give feedback.
All reactions