Troubleshooting SEB Server 1.5.2: Exception during Login #100
Answered
by
anhefti
imrhlrvndrn
asked this question in
Q&A
-
I encountered a Additionally, I'm relatively new to SEB Server and would appreciate guidance on resources or tutorials that provide comprehensive instructions on setting up and effectively using SEB Server 1.5.2. Any community-recommended guides or resources would be immensely helpful. Thank you in advance for your assistance! |
Beta Was this translation helpful? Give feedback.
Answered by
anhefti
Jan 9, 2024
Replies: 2 comments 2 replies
-
|
Hi and thanks for using SEB Server A brief analysis of the logfile you've presented, I see that the NullPointerException is just a follow-up-error but not the real cause of the problem. The source of the problem seems to be an incomplete setup preparation that causes the Webservice part of SEB Server is not able to startup properly. If you have a look at the very beginning of the logs you can see the different Docker-Containers startups and recognize the following lines:
This means that the seb-server-setup container that initializes secrets for the first time on startup was not able to find or read the "secret" File that must be created on first installation as described in the installation guide basic setup in Step 5 Maybe there was a mismatch between different kind of setups. As you can see in the installation guide the basic setups are deprecated and we highly recommend the Dockerhub Setups where we improved the setups process and also get the SEB Server image directly from Docker Hub service. We are currently working on improving the setup process for SEB Server and will delete old setup methods soon for clarity and also working on an installer for testing SEB Server on normal desktop machines. You can find the links to the Installation Guide as well as the link to the User Guide also on the Github page of SEB Server Best regards |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Hey @anhefti, Thank you for your prompt and detailed analysis. I'm currently in the process of configuring the SEB Server based on your guidance. We're running the docker containers locally for examining the potential of SEB Server. To ensure a smooth setup, I'd like to seek clarification on a few configuration parameters for the server.
|
Beta Was this translation helpful? Give feedback.
-
|
Additionally, considering our current challenges with the SEB Server, I've been pondering the possibility of altering our deployment strategy. Specifically, I'm interested in exploring the option of removing the Docker segment and instead compiling the Java code to run it directly on a cloud server. This approach may offer us greater flexibility and control over the deployment environment. However, I'm uncertain about the exact steps and intricacies involved in achieving this setup. Essentially, I'm seeking guidance on how we can effectively replicate the functionality of the SEB Server, excluding the Docker segment, and successfully run it on a cloud server. Your insights and expertise in this matter would be immensely valuable. Could we arrange a discussion or could you provide some instructions or resources to get started with this process? PS: We're a team of JavaScript developers. I would appreciate it if you could suggest steps to decouple SEB Server from Docker. What changes can we expect to the current configuration files like |
Beta Was this translation helpful? Give feedback.
-
|
Hi For a proof of concept or demo setup on a local environment, I would recommend to use the dockerhub setup under:
from the seb-server-setup repository since this is the most straight forward one for a quick setup at this time. The detailed setup guide can be seen here. This contains a bundled setup with sebserver, database and reverse-proxy all in one docker-compose setup. The revers-proxy configuration (nginx) has a preconfigured self signed TLS certificate for secure HTTPS connection. You can use this for demo put should run with own provides real TLS certificates in production. The docker-compose file looks like this: If you don't want to use HTTPS but only HTTP you can configure the reverse proxy to just forward traffic form your preferred port to the internal sebserver container. Important is that it is the reverse proxy that connects to the host and to the outside world not the sebserver service itself. But the sebserver service must known the external URL for connection data. Easiest way if you want to setup the service on our local device to say localhost you can set the following: servername is you DNS servername so either localhost or your DNS server name from where your host can be accessed via HTTP(S)
For a cloud setups you will need a more advances setup that allows you to separate and scale the different parts of SEB Server. The seb-server-setup repository gives an example of such a setup for Kubernetes. To understand to architecture and different setup for SEB Server in depth, we recommend reading the installation guide.
We hardly advise not to decouple SEB Server setup and its different component from docker since this is already doing all the hard stuff to be able to setup the different components in different environments and also to scale the components when needed. We also can not give any support for that. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
imrhlrvndrn
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
For a proof of concept or demo setup on a local environment, I would recommend to use the dockerhub setup under:
from the seb-server-setup repository since this is the most straight forward one for a quick setup at this time. The detailed setup guide can be seen here. This contains a bundled setup with sebserver, database and reverse-proxy all in one docker-compose setup.
The revers-proxy configuration (nginx) has a preconfigured self signed TLS certificate for secure HTTPS connection. You can use this for demo put should run with own provides real TLS certificates in production.
The docker-compose file looks like this:
If you don't want to use HTTPS …