web interface on non-standard port 83 (which works as expected), I have the terminal set to port 2323 (which telnets as expected) however the ftelnet from ecweb4 hangs on "Redirecting to server... ". Is there extra configuration setting that need to be adjusted?
Re: Sync Web 4
By: Mortifis to All on Wed Jan 09 2019 13:31:20
web interface on non-standard port 83 (which works as expected), I have the terminal set to port 2323 (which telnets as expected) however the ftelnet from ecweb4 hangs on "Redirecting to server... ". Is there extra configuration setting that need to be adjusted?
There's also a websocket server that should now be running, which is what ftelnet actually connects to.
Check in services.ini for a [WS] entry, and look at what port it's using. Might be 1123. Make sure that outside clients can connect to your BBS on that port.
---
echicken
Check in services.ini for a [WS] entry, and look at what port it's using. Might be 1123. Make sure that outside clients can connect to your BBS on that port.
Re: Sync Web 4
By: echicken to Mortifis on Wed Jan 09 2019 13:11:11
Hi echicken!
First, thanks for your work with the webv4, it is a nice web interface for Synchronet :)
Check in services.ini for a [WS] entry, and look at what port it's using. Might be 1123. Make sure that outside clients can connect to your BBS on that port.
I was successful configuring that, it works nicely; but I have a question: is it possible to publish only the secure one (WSS)? I was not able to get the fTelnet working by just publishing WSS, I had to publish both, WS and WSS.
I was successful configuring that, it works nicely; but I have a question: is it possible to publish only the secure one (WSS)? I was not able to get the fTelnet working by just publishing WSS, I had to publish both, WS and WSS.
The WSS service is only used for HTTPS web connections (by fTelnet). So if you only want to support HTTPS users/connections, then I think yeah, you should be able to eliminate the WS service.
What happened when you had only a [WSS] section and no [WS] section in your services.ini file? Was there an error message in your services or webserver log?
As I explained to digital man, you are both right. WS is not needed at all as long as I am browsing the web with HTTPS, as fTelnet will use then WSS. I was confused because my reverse proxy was terminating the TLS traffic and that's the reason because it was not working with WS disabled for me.
By the way echicken, now that I have the chance to talk with you... Have you considered to include the BOOTSTRA.386 as an official theme alternative for web4? I tested it and it was showing -almost ok- and I think it would only require minimal changes to make it look nice.
themes, but they should be easy to drop in. If the changes required for this one *are* minimal and don't break the stock theme, then I'm not opposed. What parts of it don't quite work / what changes do you think are needed?
Mostly font and background coloring issues. I have setup the theme in my
* Sidebar font coloring and maybe the background.
* In Forum, font and background coloring:
* In User list, the same, coloring issues.
* In the Forum messages, button or background coloring:
* In Games you can find the only layout issue I was able to identify, related to the HTML lists <ul> and <li>.
Also, in the error log the web was reporting an issue regarding a redeclaration of the settings variable in file /api/events.ssjs, I was able to fix that by making the const a regular var:
Here's some stuff that may help if pasted into the bottom of custom.css:
Pretty sure I fixed that a few days ago. When did you last update?
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495940:24:05 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,975 |