Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Glenn ten Cate
@blabla1337
and you installed Kubernetes on it as well or?
if not then you need to do that first :)
this looks like a good guide for it
https://www.howtoforge.com/tutorial/how-to-install-kubernetes-on-ubuntu/
seenu0991
@seenu0991
@blabla1337 how to disable the skip login option
@blabla1337 thanks for the guide
gruntz
@gruntz
Hello everyone. I have a working SKF instance with docker, as from blabla1337 github page. However, when I add a new user, they do not get a mail with id and pin and so on. Can someone point me to a place where I can find how to set up the mail config? I have working postfix mail with relay server, but i guess SKF is not using it. I did not found any information in the docker compose file for mail configuration.
Glenn ten Cate
@blabla1337
@gruntz yes indeed we do not mail them, you should get a popup on the page when you create the user stating the , user id and the pin code
you can then give this to the user who wants to register an account
gruntz
@gruntz
Thank you Glenn. That was helpful. Best regards.
genkoman
@genkoman
I am still struggling to run the skf using locally installed MySQL Server. Can someone please advise how exactly the docker-compose.yml should look like in order to use the locally installed MySQL Server? Thanks!
1 reply
Mohan Rajanna
@mohanrajanna15
@JorisWijnen : I have the same problem.. cannot activate admin account .. I installed on AWS EKS cluster .. The network tab in browser console shows the calls are not working properly... Did anyone have the same problem?
image.png
2 replies
Glenn ten Cate
@blabla1337
@genkoman what you need to do is then change this line to your local instance:
https://github.com/blabla1337/skf-flask/blob/816bef9c4f4c81ca22e8a6b09744f4ffc519d3a3/docker-compose.yml#L62
also you can remove from the compose file the mysql part line 15 - 25 and the line on 41 and 53
@mohanrajanna15 Hmm I see its a bit tricky here as you are accessing it on localhost?
but the calls go to the domain name
so please share your k8s yaml files you adjusted
so I can have a look and see what's maybe wrong?
you can also send it to me in the 1 on 1 chat
Mohan Rajanna
@mohanrajanna15
@blabla1337 : I have added all the files in a private chat
vegetable lasagna
@darrensmale_twitter
Hi all,
Is there any way as Admin to retrieve an access token after it's already been displayed? Or to delete a user to generate an access token for that same email?
1 reply
telekomancer
@telekomancer
hello everybody
@blabla1337 i guess that it's better to check the documentation to see if everything is ok
telekomancer
@telekomancer
imagen.png
imagen.png
Mohan Rajanna
@mohanrajanna15
@telekomancer : Do you know how to make labs work? when I use it via demo website I cant seem to reach the labs server.
image.png
image.png
Riccardo ten Cate
@RiieCco
Hey @mohanrajanna15 the lab is exposed over http ^^
1 reply
Mohan Rajanna
@mohanrajanna15
@RiieCco : Thanks Mate!!! .. I did not notice browser was redirecting it to HTTPS.
Mohan Rajanna
@mohanrajanna15
image.png

I installed skf using K8s .. when I access labs and click on start I get no response.

"b\"{'message': 'Failed to deploy, error no host or port!'}\""

image.png
telekomancer
@telekomancer
@mohanrajanna15 i guess that i can help you with that, i need to mount a lab on k8s to test that functionality (the labs), your pods are over some cloud provider, bare-metal, virtual machine ... localhost ?
Sorry for the delay, weekends are "no computer" to me
:')
Mohan Rajanna
@mohanrajanna15
@telekomancer : AWS...
telekomancer
@telekomancer
perfect, i guess that we can dig in on that, meanwhile, can you test on minikube with a local environment to test labs environment ?
if localenvironment work, probably the issue comes from AWS, LB and Ingress deployment
Mohan Rajanna
@mohanrajanna15
@telekomancer : I tested it on Minikube and did a Kube-portforward.. I was able to launch labs
telekomancer
@telekomancer
great! so the problem looks like that comes between internal communication and "external world"
Mohan Rajanna
@mohanrajanna15

@telekomancer : I can curl the labs website from the backend pod... with my deployment I still get the same error.. additionally I see the below in logs

2021-01-19 17:20:18,907 - gunicorn.error - DEBUG - GET /api/interactive_labs/deployments/lfi
ERROR:root:[Errno 2] No such file or directory: 'aws': 'aws'
ERROR:root:[Errno 2] No such file or directory: 'aws': 'aws'
ERROR:root:[Errno 2] No such file or directory: 'aws': 'aws'
ERROR:root:[Errno 2] No such file or directory: 'aws': 'aws'

telekomancer
@telekomancer
sorry for the delays
@mohanrajanna15 i can check that tomorrow
so if you are doing test's and works, please can you documentate the workaround
so sorry for the times, this week is a real madness to me
Mohan Rajanna
@mohanrajanna15
@telekomancer: I understand, the only workaround is to really switch context to minikube. when I switch to AWS I start seeing those errors. I haven't been able to fix that problem.
telekomancer
@telekomancer
I understand, i can test the deploy at homelab with rancher and other stuff, so can you please send me your yaml files, please modify the neccesary information to test the deployment and/or ip's for generic domains and generic ip's, so if you have, for example: skf.contoso.com, change it to skf.homelab.lan, and the ip's (or even LB configs), to some generic to understand if their are internal, public, localhost, so if your ip's are public, change it to 1.1.1.1, or if their are exposed to lan, change it to 192.168.1.2, for example, now, if their are localhost, please left them intact. Feel free to send me that information via internal message if you want =)