Hello, Quick question. Does it make any difference...
# support-questions-legacy
x
Hello, Quick question. Does it make any difference in implementing https for the frontend and backend? In the config files, the websiteUrl and apiUrl are called with http. Thank you
r
hey @xewonder_83908 using http vs https does make a diff in how cookies work with the browser.
x
Hi, I tried all day to make it work but running into all sorts of problems with the websocket and reverse proxy on Apache. I can not find any documentation. Any pointers?
r
uhmm. What is the problem? The description is very vague, and im not sure if it's even related to supertokens
x
For testing, i have core, backend and frontend running on the same server with the original ports 3567,3000 and 3001
i have 3 subdomains for the 3 services
in the conf of apache i have 3 different configurationss for the subdomains. all with "proxypass" and "proxyreverse" for https
this works in showing the backend and frontend pages
however, in teh front end i get this:
r
this seems like an apache config issue
Basically the frontend can't reach the backend server
what does the browser console say?
x
Firefox can’t establish a connection to the server at wss://toxxxx-xxx.com:3000/ws
r
not sure. Sorry. This does not really seem to be an issue with supertokens integration
x
this is in my apache config:
ProxyPass /ws ws://localhost:3000/ws ProxyPassReverse /wd ws://localhost:3000/ws
r
can't help with apache config here
good luck!
x
is it safe to leave it at http?
.... i guess not...
thank you anyways!