What is the default user/password for CMDB? I can see in the .env that a tenant CMDB is being created, but i cannot login.
Cheers

Expected behavior

Run docker Image. Test API.
Because testing on a production instance is not a good idea.

Actual behavior

Run docker image. No API Module is found.
Forget the idea because, reinstalling the Addon over GUI is no fun.

Steps to reproduce the behavior

See README in https://github.com/alexei-matveev/hello-idoit

Environment

Hello,

why is AllowOverride in all vhost.conf files set to None? This disables mod_rewrite defined in .htaccess which breaks some parts of the i-doit installation.

Can the setting be changed to "All" in correspondance with non-docker installations? I will gladly provide a patch.

Regards,
Sebastian Mischke

Can anyone guide how to configure SSO in i-doit with apache server ?

I would like to doublecheck that the LDAP over SSL configuration should be working in these docker images. Everything else seems to work great! The exact ldap configuration does work with other software, so I suspect something is missing/unconfigured in the docker image. I have also installed openssl in the idoit container, to validate certs and connectivity, output in logs below does show it should work.

Expected behavior

I would expect the ldap over SSL to work, after configuring.

Actual behavior

ldap debug windows says:

Error!
LDAP Bind failed (Can't contact LDAP server). Host: ldaps.domain.com

Steps to reproduce the behavior

Configure ldap server, enable LDAPS in de TLS field

Environment

Server logs

[2021-03-22T11:31:18.259787+01:00] ldap.DEBUG: Testing connection to ldaps.domain.com:636 (CN=<SNIPPED>) [] []

openssl s_client -connect ldaps.domain.com:636
CONNECTED(00000003)
..
SSL handshake has read 3812 bytes and written 487 bytes
Verification: OK

Verify return code: 0 (ok)

Expected behavior

Start of docker image using the example code.

Actual behavior

Fails with error.

Steps to reproduce the behavior

docker run --name i-doit-apache -p 6080:80 bheisig/idoit:1.14-pro-php7.4-apache

docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "entrypoint.sh": executable file not found in $PATH": unknown.
ERRO[0006] error waiting for container: context canceled

I mounted the image and found "entrypoint.sh" without execute rights:
root@c2:~/docker/i-doit# ll /mnt/usr/local/bin/entrypoint.sh
-rw-r--r-- 1 root root 259 Jan 31 23:08 /mnt/usr/local/bin/entrypoint.sh

Environment

Server logs

Expected behavior

i-doit search should be working...

Actual behavior

Search is not working.

Steps to reproduce the behavior

Using the latest apache based image bheisig/idoit:1.13.2-open-php7.3-apache:
When typing a search key into the search field and hitting enter, apache answers with a 404 Not found.

Environment

Server logs

[Wed Nov 13 09:30:41.139297 2019] [core:info] [pid 19] [client 172.17.0.1:37974] AH00128: File does not exist: /var/www/html/search, referer: http://localhost/
172.17.0.1 - - [13/Nov/2019:09:30:41 +0000] "GET /search?q=asdf&rand=1573637441110 HTTP/1.1" 404 271
[Wed Nov 13 09:30:41.279861 2019] [core:info] [pid 19] [client 172.17.0.1:37974] AH00128: File does not exist: /var/www/html/search, referer: http://localhost/
172.17.0.1 - - [13/Nov/2019:09:30:41 +0000] "GET /search?q=asdf HTTP/1.1" 404 271

Steps to FIX the behavior

The apache VHost configuration needs to be adjusted to alllow overrides from the i-doit shipped .htaccess file:

...
        AllowOverride All
...

instead of None.

Expected behavior

It should be possible to update i-doit by pulling a new image. There must be a logic to check whether DB backend needs an update. If check is positive then update should be performed in background before container is ready for connections.

Additionally, we should work with version independent tags, for example open-apache-latest.

Actual behavior

Update logic hasn't been implemented yet.

Steps to reproduce the behavior

1. Run image with older version
2. Pull new image
3. Restart container

Environment

Any

Need help

Hi,
I don't understand how to use the docker files. When trying the given command, I get a permission errer, although i am logged in. As you can see in the first Part of the Console-Log the pull request with your repository works, but the run-command doesn't.

Server logs

root@debian9:/home/jan# docker pull  bheisig/idoit:1.13-pro-php7.3-apache
1.13-pro-php7.3-apache: Pulling from bheisig/idoit
fc7181108d40: Already exists
0e65236fc68a: Already exists
657b7ad8209d: Already exists
fe9abd6f2547: Already exists
3f3b3b58af14: Already exists
6c87b44c0319: Already exists
879171658515: Already exists
29c3b2e8a58a: Pull complete
c3a25239431e: Pull complete
12d528342619: Pull complete
9c2154884a2a: Pull complete
65330d5bd097: Pull complete
09bf81aa1690: Pull complete
51b06b672862: Pull complete
8e3891a5acf6: Pull complete
9f63ae12fd0c: Pull complete
533e8ba4d71c: Pull complete
64df962b8743: Pull complete
8c6f109d2fbc: Pull complete
Digest: sha256:241ea3a64b212e107ec3aaf5488573a3f0d0beba309252f40d341b3e9096ff36
Status: Downloaded newer image for bheisig/idoit:1.13-pro-php7.3-apache

root@debian9:/home/jan# docker run i-doit-apache -p 80:80 bheisig/idoit:1.13-pro-php7.3-apache
Unable to find image 'i-doit-apache:latest' locally
docker: Error response from daemon: pull access denied for i-doit-apache, repository does not exist or may require 'docker login'.
See 'docker run --help'.

Expected behavior

Object browser shows objects

Actual behavior

Object browser shows none

Steps to reproduce the behaviour

Spin up a fresh instance, 1.15 or 1.14 --- same behaviour.
Add a couple of servers try linking them with Person Groups or Service.
You get an object browser popup with no actual objects.
Independent of version --- that maybe an indication of an issue in
infrastructure (Image?).
See here for an exact setup: https://github.com/alexei-matveev/hello-idoit

The message like this

File does not exist: /var/www/html/cmdb/browse/objectType/31

is a strange thing to get from a MySQL based product ...

Environment

Same behaviour with 1.15 too ..

Server logs

10.42.0.1 - - [23/Oct/2020:18:39:20 +0000] "POST /?mod=cmdb&popup=browser_object_relation&ajax=1 HTTP/1.1" 200 9302
[Fri Oct 23 18:39:20.867626 2020] [core:info] [pid 28] [client 10.42.0.1:33960] AH00128: File does not exist: /var/www/html/cmdb/browse/objectType/31, referer: http://idoit.localhost/?call=category&objID=28&viewMode=1002&tvMode=1006&catgID=78&page=1&filtered=1&tableFilter%5Boperation%5D=-1
10.42.0.1 - - [23/Oct/2020:18:39:20 +0000] "POST /cmdb/browse/objectType/31 HTTP/1.1" 404 277

Expected behavior

Using IDOIT_WEB_PORT=9000 in .env and running docker-compose -f docker-compose-apache.yml up, I can launch i-doit at http://localhost:9000/i-doit.

Actual behavior

Browser reports ERR_CONNECTION_RESET error.

Steps to reproduce the behavior

See expected behavior

Environment

Expected behavior

Login to i-doit using URL http://localhost:8080/ or http://localhost:8080/i-doit/ or http://localhost:8080/i-doit/admin/

Actual behavior

The error "Database error : No such file or directory" appears.
The command "docker-compose logs|grep denied" give the following output:
db_1 | 2020-11-01 0:29:17 8 [Warning] Access denied for user 'root'@'i-doit-docker_idoit_1.i-doit-docker_backend' (using password: YES)
db_1 | 2020-11-01 0:29:17 9 [Warning] Access denied for user 'root'@'i-doit-docker_idoit_1.i-doit-docker_backend' (using password: YES)

Steps to reproduce the behavior

Build a new docker installation using docker-compose-fpm.yml and .env.dist only changing IDOIT_WEB_PORT=8080.

Environment

Server logs

db_1 | 2020-11-01 0:29:17 8 [Warning] Access denied for user 'root'@'i-doit-docker_idoit_1.i-doit-docker_backend' (using password: YES)
db_1 | 2020-11-01 0:29:17 9 [Warning] Access denied for user 'root'@'i-doit-docker_idoit_1.i-doit-docker_backend' (using password: YES)