Hi,

I'm having an issue with retrieving emails when osTicket has no tickets in memory.
It reads the email fine, deletes it, and opens the ticket on osTicket. However,
if there are tickets in memory, osTicket will read the email but will not delete it nor download it.
As soon as I delete the existing ticket, it downloads the emails and deletes the pending emails.

Thanks
Cédric

I’m trying this image, with the target to containerize an existing on-premise and in-production installation.

So I started to play with the image in a non-production environment.

In a such condition, I was able to:

• Use the latest image and even building the v1.18 image separately (using the Dockerfile found on v1.8 branch).
• Use the above images with MySQL v8.0.35 (aligned to my current in-production DB engine).

Thrilled with this first good result, I then read the rest of README instructions on how to persist the secret.txt file, mount my db- and app-volumes (in the perspective to use them in production), finally I developed a docker-compose.yml (a little bit different from the original one, based on my needs, you can find it here).

But when I re-created the containers, suddenly I could't log in the SCP anymore with the default credentials.

I also tried to reset the ostadmin password as suggested here, but with no joy.

And this happens even if I go back to using the command-line methods proposed in the README.

It seems that I can recover the possibility to enter in the system only by an insane repetition of tear-down and re-creation of containers.

How can this be possible? Any thoughts?

The health status of the container is still "starting", even if the container is already started. I see you make a HEAD request to check if nginx is alive, but unfortunately either nginx or osticket is returning a 400 error to a HEAD request.

This is problematic if we use Traefik as a reverse-proxy, since Traefik manage only safe containers (and not starting containers).

Hello,

I'm trying to install this on my unraid server and when I put the direct database ip, username and password, all variables, it doesn't work due to it not having a port listed. My MariaDB container aborts the connection because of the no port.

When I add the port to the ip, ie: 1.1.1.1:3306 it get stuck waiting for TCP connection.

It goes through waiting for about 2 minute or so then stops the container since it can't connect.
My MariaDB container doesn't receive a connection request.

I added the Variable MYSQL_PORT to see if that would work and removed the port from the MYSQL_HOST variable but it doesn't notice the port.

Could the MYSQL_PORT variable be added to the container?

I'm not sure this would fix the issue.

My joomla website and Nextcloud have no issues with connecting to the database.

Even when using the hostname of the MariaDB container(MariaDB) it just waits for the TCP connection.

Hi,

The Dockefile is downloading outdated i18n files. The files are downloading from "https://s3.amazonaws.com/downloads.osticket.com/lang/${lang}.phar;" but the update file that I got in oficial osTicket site is "https://s3.amazonaws.com/downloads.osticket.com/lang/1.14.x/${lang}.phar".

My problem specially is with pt_BR translate, the field "E-mail and Username" has a horrible translate error.

Thanks,

When using the default logins from the settings, it does not enter:

Please, can you upgrade the package to version 1.11 final release?

Thanks

Have everything set up and running great so far (thanks).

Would like to configure for HTTPS but it doesn't appear that it is enabled in the image.

Can it be configured or can you add it to the image?

Thanks in advance.

I believe this might be an issue with this container, since there is no one complaining of this issue since JAN2020 on the official forums. Maybe this container is missing some dependency, or uses wrong version of some dependency?

It looks like we build already installed PHP extensions.

In order for email processing to work, I had to enter the container, use crontab -e to edit the list of cronjobs and add the following line:

*/1 * * * * php /var/www/html/api/cron.php

Hi,

healthcheck fails - curl request returns 400

curl request:

/var/www/html # curl -fIsS http://localhost/
HTTP/1.1 400 Bad Request
Server: nginx
Date: Thu, 09 Nov 2023 09:53:41 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 23
Connection: keep-alive
Set-Cookie: OSTSESSID=vda754cu6u7vc4pu881vcop36e; expires=Thu, 09-Nov-2023 10:17:41 GMT; Max-Age=1440; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

curl: (22) The requested URL returned error: 400
/var/www/html # curl -fIsS https://localhost/
curl: (7) Failed to connect to localhost port 443 after 0 ms: Couldn't connect to server
/var/www/html # curl -fIsS http://localhost/
HTTP/1.1 400 Bad Request
Server: nginx
Date: Thu, 09 Nov 2023 09:54:30 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 23
Connection: keep-alive
Set-Cookie: OSTSESSID=jn36u7umav1javutggsvuulkuk; expires=Thu, 09-Nov-2023 10:18:30 GMT; Max-Age=1440; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

curl: (22) The requested URL returned error: 400

compose file:

version: '3.7'

services:
  osticket:
    image: devinsolutions/osticket
    container_name: osticket
    restart: unless-stopped
    volumes:
      - www:/www/osticket
      - logs:/www/logs
    environment:
      - MYSQL_HOST=osticket_db
      - MYSQL_ROOT_PASSWORD=******
      - MYSQL_DATABASE=osticket
      - MYSQL_USER=osticket
      - MYSQL_PASSWORD=******
      - INSTALL_SECRET=******
  
      - TIMEZONE=Europe/Warsaw
      - CRON_INTERVAL=10
      - SMTP_HOST=******
      - SMTP_PORT=25
      - SMTP_FROM=******
      - SMTP_TLS=0
      - SMTP_USER=******
      - SMTP_PASS=password

      - INSTALL_NAME=******

      - ADMIN_FIRSTNAME=******
      - ADMIN_LASTNAME=******
      - ADMIN_EMAIL=******
    ports:
      - 8080:80
    networks:
      - osticket_network
      - waf-proxy_proxy_network
    depends_on:
      - osticket_db

  osticket_db:
    image: mariadb:latest
    container_name: osticket_db
    volumes:
      - db:/var/lib/mysql
    environment:
      - TIMEZONE=Europe/Warsaw
      - MARIADB_ROOT_PASSWORD=******
      - MARIADB_DATABASE=osticket
      - MARIADB_USER=osticket
      - MARIADB_PASSWORD=******
    restart: unless-stopped
    networks:
      - osticket_network

networks:
  osticket_network:
  waf-proxy_proxy_network:
    external: true
volumes:
  www:
  logs:
  db:

Issue :: Docker Image Build Fails

Step 4/11 : RUN --mount=type=bind,source=utils/verify-plugin.php,target=/tmp/verify-plugin.php,readonly the --mount option requires BuildKit. Refer to https://docs.docker.com/go/buildkit/ to learn how to build images with BuildKit enabled

This happens with newer Docker versions:

docker version

Client:
 Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.6
 Git commit:        ced0996600
 Built:             Wed Jul 26 21:44:58 2023
 OS/Arch:           linux/amd64
 Context:           default

I am not yet familiar with BuildKit. But a quick-fix is to replace the RUN mount in build step 4 with a COPY:

COPY utils/verify-plugin.php /tmp/verify-plugin.php

RUN set -ex; \
...

I set an admin user name and password via the docker variables. yet those credentials do not work when trying to log in to the web UI. Also tried the default ostadmin/Admin1 and that combo did not work.

What step am I missing?

Running on UnRaid if that matters and connected to MariaDB.

I created docker container and setup SMTP properly. I send some emails for testing and there is the result.

Source of email send by osticket looks like that :

From: =?utf-8?Q?[Example]=20Customer=20service?= [email protected]
Subject: =?UTF-8?Q?Re:=20test2=20[#173295]?=
In-Reply-To: [email protected]
References: [email protected]
X-Mailer: =?UTF-8?Q?osTicket=20Mailer?=
To: =?utf-8?Q?d?= [email protected]

Google and other mark that email as potential spam because it shows that "From" is wrongly formatted. I would expect something like that:

From: [Example] Customer service [email protected]
Subject: Re: test [#173295]
In-Reply-To: [email protected]
References: [email protected]
X-Mailer: osTicket Mailer
To: [email protected]

I don't know nothing abount php so can't figure out where is the problem but it must be something with utf8 encoding.

Hi,

is there any manual on how to upgrade from one version to another.

Thank you and best regards
Damjan

Hey, I am trying to get outgoing email to work with this image via the environment variables, and have been having issues.
I've used:
SMTP_HOST
SMTP_PORT
SMTP_FROM
SMTP_USER
SMTP_PASSWORD

and I'm sure all this information is correct, but once I log into the admin control panel and go to email settings, I don't see my email there, and when I go to diagnostics and try to send a test mail it doesn't work. Do you mind helping me get this working?

Hi there,

Thanks for this fork... I was using CampbellSoftwareSolutions one previously, which was fine for the most part.. but after facing issues being unable to upgrade to 1.14.1, I stumbled across your fork.

So, I appear to have upgraded semi-successfully, most things appear to be working... but the subject field is missing from the ticket queue

despite the ticket actually having a subject:

I've confirmed all past tickets are displaying the same behaviour.

Just wanted to check with you before I go to the osTicket forums, as it may be something specific to your image. Or could it be that the database upgrade was not so smooth?

Changing things in the Columns tab of the queue settings does not appear to persist...

Compose file:

version: '3.4'
services:
  mysql:
    container_name: mysql
    restart: unless-stopped
    image: mysql:5.7.22
    environment:
      MYSQL_ROOT_PASSWORD: [PASSWORD]
      MYSQL_DATABASE: osticket
      MYSQL_PASSWORD: [PASSWORD]
      MYSQL_USER: osticket
    volumes:
      - ./mysql/:/var/lib/mysql
    ports:
      - 3306:3306

  osticket:
    container_name: osticket
    restart: unless-stopped
    image: devinsolutions/osticket
    depends_on:
      - mysql
    environment:
      INSTALL_SECRET: [SECRET]
      MYSQL_HOST: mysql
      MYSQL_PASSWORD: [PASSWORD]
      CRON_INTERVAL: 1
    image: devinsolutions/osticket:1.14.1
    ports:
    - 8080:80

My logs in osticket are showing the Docker IP ranges. I assume we need to set TRUSTED_PROXIES in the config.

Can you add that as a variable

Also I assume there will need to be an nginx config to use the forward ip?

I believe osticket uses X-Forwarded-For header

I've followed the upgrade instructions, but when I update my docker container to 1.17.2 and then log in with my offline account, I'm not prompted to update on the System Information page. It tells me that I'm still running v1.16.3 (e148727) and that v1.16.5 is available (on osticket's website). I'm using the repository:

devinsolutions/osticket:1.17.2 (or devinsolutions/osticket:latest)

Interestingly, my ldap logins aren't working when running this version, just the offline admin account I've created. When I change back to devinsolutions/osticket:1.16.3 all of my login accounts work as expected. Am I missing something?

Can you add docker-compose for arm cpu?

After select in admin panel timezone Kyiv Osticket not correct work and not accept login admin

When enabled "Help Desk Audit" plugin, works on agents and tickets web interfaces.

But it crashes on Admin Panel -> Dashboard -> Audit Logs.

This is the error displayed.

Fatal error: Uncaught Error: Failed opening required 'phar:///var/www/html/include//plugins/audit.phar/class.audit.php' (include_path='./:/var/www/html/include/:/var/www/html/include/pear/') in /var/www/html/scp/audits.php:19 Stack trace: #0 {main} thrown in /var/www/html/scp/audits.php on line 19

this is the content of the related directories

/var/www/html # ls -al include/plugins/
total 52
drwxr-xr-x 1 root root 4096 Sep 2 04:27 .
drwxr-xr-x 1 root root 4096 Sep 6 18:30 ..
-rw-r--r-- 2 root root 0 Sep 2 04:27 .keep
drwxrwxr-x 3 root root 4096 May 31 10:48 audit
drwxrwxr-x 3 root root 4096 Sep 2 04:27 auth-2fa
drwxrwxr-x 3 root root 4096 Sep 2 04:27 auth-cas
drwxrwxr-x 3 root root 4096 Sep 2 04:27 auth-ldap
drwxrwxr-x 3 root root 4096 Sep 2 04:27 auth-oauth
drwxrwxr-x 2 root root 4096 May 31 10:48 auth-passthru
drwxrwxr-x 2 root root 4096 May 31 10:48 auth-password-policy
drwxrwxr-x 2 root root 4096 Jul 18 2017 slack
drwxrwxr-x 2 root root 4096 May 31 10:48 storage-fs
drwxrwxr-x 3 root root 4096 Sep 2 04:27 storage-s3
-rw-r--r-- 2 root root 1194 Sep 2 04:27 updates.pem

/var/www/html # ls -al include/plugins/audit/
total 68
drwxrwxr-x 3 root root 4096 May 31 10:48 .
drwxr-xr-x 1 root root 4096 Sep 2 04:27 ..
-rw-rw-r-- 1 root root 7312 May 31 10:48 audit.php
-rw-rw-r-- 1 root root 37994 May 31 10:48 class.audit.php
-rw-rw-r-- 1 root root 647 May 31 10:48 config.php
-rw-rw-r-- 1 root root 418 May 31 10:48 plugin.php
drwxrwxr-x 2 root root 4096 May 31 10:48 templates
/var/www/html #

I have had osTicket running using this image together with mariadb container on Ubuntu 18.04 extremely well for the last few weeks.
Today I ran all the recent 18.04 updates/upgrades (still remaing on 18.04) after which osticket appears to not be able to connect to the database container.

Docker log for osticket says
`== MANUAL INTERVENTION MAY BE REQUIRED IF UPGRADING FROM 1.16.3 OR EARLIER ==

If you are upgrading from an image tagged 1.16.3 or earlier, there may be
breaking changes related to how plugins are shipped in this image.

Please, take a moment to read
https://github.com/devinsolutions/docker-osticket#upgrading, and perform manual
intervention if required.

== MANUAL INTERVENTION MAY BE REQUIRED IF UPGRADING FROM 1.16.3 OR EARLIER ==
Configuring mail settings
OSTicket cron job is set to run every 5 minutes
Using linked MySQL container
Waiting for database TCP connection to become available...
Waited for 15 seconds...
`

The mariadb container seems to be running fine and I can still connect to it from the host machine (i pull osticket database stats into Grafana via the host). Also I can access the database from the host using mysql -u -p and see all the osticket tables etc.

However, if i go into the osticket bash shell I can ping the mariadb container BUT I cannot netcat to 3306 (ie nc 172.17.0.2 3306 fails).

Thinking so far that either something is broken in the docker --link feature or I have some sort of other problem that is preventing osticket from seeing the database container.

I've been at this for several hours so just hoping for inspriation from others.

If it helps here are the commands Im using to start the two containers (some data redacted)
docker run --name osticket_mysql -d -v /root/dockersql:/var/lib/mysql -e MYSQL_HOST=localhost -e MYSQL_DATABASE=osTicket -e MYSQL_USER=ostuser -e MYSQL_PASSWORD=yyyy -e MYSQL_ROOT_PASSWORD=xxxx mariadb

docker run -d --name osticket --link osticket_mysql:mysql -e SMTP_HOST='smtp.mxxxxxxxxxxxxxxxxxxxd.co.uk' -e SMTP_USER='[email protected]' -e SMTP_TLS=1 -e SMTP_PORT=465 -e SMTP_PASSWORD='xyxyxy' -e MYSQL_USER=ostuser -p 8080:80 devinsolutions/osticket

Thanks in advance for any ideas.

Mike

Hello,

currently running 'devinsolutions/osticket'

Not sure if this is normal, but the 'Data Path' mapping on has not data/file.

navigating to '/mnt/user/appdata/osticket/' has no data/files is this normal while using mysql/mariadb database?

Any way so I can migrate a full populated setup running container from osticket [1.12.3] to the latest version of that image and rollback in case of failures ?

Update: typo

Hi there, Great to see a working container of osTicket! Was wanting to try build one but always struggled for some reason?

Anyways. I cloned your repo and tried to update the SHA256 and version from 1.16.1 to 1.16.3 but when trying to build the Dockerfile, it keeps throwing errors.
Do you have any suggestions on how I can push this to the latest stable? or if we can set it as an ENV going forward on your repo?

Hi. Can this image be updated to pull the latest osticket version?